Checked on 2026-11-14, before implementing the corresponding integrations. Versions below came from npm view <package> version; API signatures were cross-checked against the published package tarballs (npm pack) and the official documentation/source. Dependencies are pinned in package manifests and the root lockfile.
| Package | Verified version | Notes |
|---|---|---|
near-api-js |
7.5.3 |
Node 22.22.2+; use the v7 single-package API for server-side signing. |
@near-wallet-selector/core |
10.1.4 |
v10 requires NEAR action objects, not v9 plain action descriptors. |
@near-wallet-selector/my-near-wallet |
10.1.4 |
Popup wallet; testnet URL is https://testnet.mynearwallet.com. |
@near-wallet-selector/nightly |
10.1.4 |
Browser extension; native signing uses the configured Testnet RPC. |
@hot-labs/near-connect |
0.12.0 |
Lazy sandbox bridge for Meteor and Intear; fixed provider manifest and no function-call key requested. |
next |
16.4.6 |
Node >=20.9; React 19 is supported. |
react, react-dom |
19.3.1 |
Application React version. |
tailwindcss, @tailwindcss/postcss |
4.3.5 |
v4 PostCSS package is separate. |
drizzle-orm |
0.45.4 |
SQLite persistence through the better-sqlite3 adapter. |
better-sqlite3 |
13.1.1 |
Node >=22; native module needs a compatible build toolchain. |
typescript |
7.0.2 |
Current registry release when checked. |
tsx |
4.23.15 |
TypeScript service/script execution. |
@playwright/test |
1.65.1 |
Browser smoke tests and screenshots. |
near-cli-rs |
0.31.1 |
Optional deployment/account CLI. |
Use Node 22.22.2 or later for the whole monorepo. The installed environment used Node 22.23.0.
Sources:
- NEAR API documentation
- Official v7 README and examples
- Published TypeDoc
- Published
near-api-js@7.5.3types:lib/index.d.ts,lib/account-BlZEm07p.d.ts.
import { Account, JsonRpcProvider, teraToGas, type KeyPairString } from 'near-api-js';
const provider = new JsonRpcProvider({ url: rpcUrl });
const bounty = await provider.callFunction({
contractId,
method: 'get_bounty',
args: { id: 0 },
blockQuery: { finality: 'final' },
});
const verifier = new Account(verifierAccountId, provider, privateKey as KeyPairString);
const outcome = await verifier.callFunctionRaw({
contractId,
methodName: 'release',
args: { id: 0 },
deposit: 0n,
gas: teraToGas('100'),
waitUntil: 'FINAL',
});provider.callFunction is a view method and takes method. account.callFunctionRaw signs a transaction and takes methodName. Gas/deposit are bigint, expressed in gas units/yoctoNEAR. callFunction returns the decoded method result; callFunctionRaw preserves transaction hash, logs and receipt outcomes. Default transaction wait is EXECUTED_OPTIMISTIC, so settlement code explicitly waits for FINAL and re-reads contract state. A resolved callback transaction alone does not prove a payout succeeded: the contract's transfer callback controls Released and points.
The library does not read environment credentials itself. Private keys stay in service/script environment variables; never expose them through Next.js public config.
Sources verified again for the multiwallet revision on November 14, 2026:
- v10 migration guide
- Core setup
- MyNearWallet adapter
- Nightly adapter
- NEAR Connect documentation
- Published
@near-wallet-selector/core@10.1.4types:src/lib/wallet/wallet.types.d.ts,src/lib/store.types.d.tsand the correspondingindex.jsimplementations. - Published
@near-wallet-selector/nightly@10.1.4src/lib/injected-nightly.d.ts;signMessagetakes the complete coreSignMessageParams. - Published
@hot-labs/near-connect@0.12.0build/NearConnector.d.ts,build/SandboxedWallet/index.js,build/types/index.d.ts, and package-shippedskills/near-connect-quickstart/SKILL.md. Types/source take precedence over the skill's older version header.
GitSettle retains Wallet Selector for account state and its v10 NEAR action objects. The custom accessible modal is independent of signing libraries. Provider metadata renders without loading any wallet SDK; selecting or restoring one provider lazily loads that provider's implementation. selector.store.observable updates account identity; disconnect and account changes also invalidate the separate private support session.
const wallet = await selector.wallet(providerId);
await wallet.signIn({ contractId });
await wallet.signAndSendTransaction({
signerId: accountId,
receiverId: contractId,
actions: [actionCreators.functionCall('claim_bounty', { id: 0 }, 100000000000000n, 0n)],
});The app's module wrappers preserve selector's contract state but do not forward a contract/key request to provider sign-in. MyNearWallet's underlying signIn({}) creates no function-call key. Meteor and Intear use SandboxWallet.signIn({ network: 'testnet' }), with no addFunctionCallKey. Nightly retains the key inside its extension. A previous MyNearWallet connection with a saved functionCallKey is blocked from starting new transactions until the user disconnects/reconnects; this removes the local copy through the adapter but does not revoke an older on-chain permission. The user can revoke it in wallet settings. No application UI accepts a private key or recovery phrase.
| Provider | Connection | Private support authentication |
|---|---|---|
| MyNearWallet | Testnet popup | Complete NEP-413 challenge, including callback URL |
| Nightly | Installed browser extension | Wrapper forwards the full native SignMessageParams; upstream selector adapter drops callbackUrl |
| Meteor Wallet | NEAR Connect sandbox / provider popup | Pinned executor forwards the full challenge, including callbackUrl |
| Intear Wallet | NEAR Connect sandbox / web or mobile | Escrow only in this revision: its executor drops callbackUrl, so GitSettle refuses support sign-in rather than weakening server verification |
The sandbox bridge uses only two explicit manifest entries with testnet and signInWithoutAddKey support. The selected SandboxWallet is constructed directly; untrusted injected events cannot replace the chosen executor. Provider scripts and wallet endpoints remain trusted dependencies. Intear stores a connector authentication key in browser storage, which is distinct from an on-chain NEAR signing key. Sandbox isolation is not an audit or a claim that providers hold no browser session data. Provider provenance and licenses are recorded alongside the pinned manifest/assets.
The old Meteor selector adapter was considered and rejected: its SDK generates a local access key and logs the key object. The HERE adapter was also excluded; its network is not inherited automatically and its SDK creates local keys. HOT, EVM providers and WalletConnect are not advertised as generic Testnet options without verifying their exact network/capability requirements. This prevents decorative wallet logos from implying a working connection.
The legacy modal-ui package is removed. Browser/popup providers may return void on navigation. Preserve pending unsigned action metadata before signing; verify transactionHashes against signer, receiver, method, arguments, finality and on-chain state before reporting success. Do not infer success from a popup closing or a URL parameter. Recover pending intent before optional wallet modules load, and keep it when a hash does not prove the original action. Payable create attaches reward plus storage reserve using exact integer arithmetic.
Sources:
- API versions
- Get a pull request
- Check whether a pull request has been merged
- List pull request files
- Issue linking and closing keywords
- REST pagination
Current documented API version is 2026-03-10. Requests explicitly send Accept: application/vnd.github+json, X-GitHub-Api-Version: 2026-03-10, and a descriptive User-Agent. Optional token: Authorization: Bearer …. Restrict request origins to https://api.github.com; do not fetch arbitrary user-supplied PR URLs with a token.
Relevant endpoints:
GET /repos/{owner}/{repo}/pulls/{pull_number}
GET /repos/{owner}/{repo}/pulls/{pull_number}/merge
GET /repos/{owner}/{repo}/pulls/{pull_number}/files?per_page=100&page=1
GET /repos/{owner}/{repo}/issues/{issue_number}
For the PR object, verify merged === true, non-null merged_at, base.repo.full_name equal to the bounty repository, matching PR number/canonical URL, and a closing reference to the exact issue in body. The merge-check endpoint is 204 if merged, 404 otherwise. When the optional merge_commit_sha audit field is null or omitted, GitSettle additionally requires that endpoint to return exactly 204. A conflicting 404, unexpected 200, outage, or rate limit remains an operational error and cannot authorize payout or reject the contribution. When the field is unavailable, evidence records merge_sha: null; it never substitutes a head commit or invents a merge SHA.
For the recorded November 14, 2026 check against real PR #10, the response requested with X-GitHub-Api-Version: 2026-03-10 omitted merge_commit_sha entirely, while the default-version API response returned it. Both supplied the required merged timestamp, repository, issue/account body evidence, and changed-file metadata; /pulls/10/merge returned 204. An allowlisted regression fixture retains only public verification fields, the two evidence lines, and file summaries in services/verifier/src/fixtures/github-2026-pr10.json. The real read-only policy check passed with merge_sha: null and locales/es/contributing.md; that check did not submit or release a bounty. Historical evidence preserves the fields observed by that run.
GitHub issue-closing semantics apply only when merging to the default branch. GitSettle's oracle checks an explicit reference; it does not claim GitHub closed the issue unless that separate fact is checked.
Recognized GitHub closing words are close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved, case-insensitive with an optional colon. Same-repository references use #123; qualified references use owner/repo#123. GitSettle may also recognize a canonical issue URL. Match number boundaries so #12 never matches #123, and repository boundaries so a qualified reference cannot accidentally match another repository.
A claimant cannot prove ownership by merely submitting someone else's PR URL. Require an exact standalone, visible PR-body line:
GitSettle: <contract_id>/<bounty_id>/<claimant_account_id>
This binds the PR to this contract, bounty, and NEAR recipient. It is evidence under the trusted-oracle model, not a cryptographic GitHub identity proof: PR bodies can be edited by the PR author and authorized maintainers. The oracle does not determine translation quality or security correctness.
The implemented closing reference starts a plain body line or an unordered list item. Comments, blockquotes and code examples do not supply evidence. A merge timestamp must be at or after on-chain bounty creation, preventing retroactive rebinding of a historical merge. An older open PR can still finish funded work.
Translation validation scans the returned changed-file paths for an exact expected locale segment in an allowed i18n/localization directory (for example locales/es/messages.json, src/i18n/bn/common.json, public/locales/ja/ui.json). It rejects removed-only changes and substring matches such as locale es matching es-MX. GitHub files pages default to 30 and cap at 3000 files total. Fetch with per_page=100, verify completeness against changed_files, and refuse automatic payout if incomplete/over cap. Use a bounded request timeout, rate-limit-aware retries and a maximum page count.
Open/unmerged PRs remain pending even after a deadline: a valid timely submission must continue protecting the claimant from refund. HTTP 403/429, outages, malformed API data, and partial pagination are retryable operational failures, never proof a submission is invalid. Only definite mismatches may be rejected, and only through the contract's verifier-authorized path.
Sources:
npx near-cli-rs@0.31.1 account create-account \
sponsor-by-faucet-service YOUR-UNIQUE-NAME.testnet \
autogenerate-new-keypair save-to-legacy-keychain network-config testnet createThe official implementation posts JSON to https://helper.nearprotocol.com/account with newAccountId and newAccountPublicKey. Generate keys locally and persist with restrictive permissions before requesting funding. Only the public key goes to the faucet. Verify the resulting account and key through testnet RPC. This creates a testnet development account, never a mainnet prize account. Availability and free balance are controlled by the public faucet.
- Next.js installation/App Router
- Tailwind with Next.js
- Drizzle SQLite setup
- Drizzle better-sqlite3 connection
SQLite is a rebuildable read-model/audit store. The NEAR contract is authoritative for reward custody, bounty state, access control, and earned points. Demo fixture rows must be visibly labeled and must never be mixed with live chain balances.