COMMUNITY · CODE BROWSER

Code

Open GitHub issues and pull requests of nearcore, near-sdk-rs, near-api-js, Chain Signatures, IronClaw and other NEAR repositories.

3,198issues and PRs

synced 1h agoGitHub

All3,198 IronClaw1,572 nearcore587 Chain Signatures (mpc)537 near-sdk-rs120 Omni Bridge54 near-workspaces-js45 near-cli-rs44 near-workspaces-rs40 cargo-near39 docs.near.org38 Intents SDK30 near-api-js26

openIssue #4343 · Chain Signatures (mpc) · barakeinav1

epoch-sync auto-recovery: bound repeated data-reset wipes

openIssue #4321 · Chain Signatures (mpc) · gilcu3

Consolidate the foreign-chain crate boundaries

openIssue #4314 · Chain Signatures (mpc) · barakeinav1

E2E integration test: epoch-sync stale-node auto-recovery (#3909)

openIssue #4308 · Chain Signatures (mpc) · netrome

Break out all logic from `evm_inspector_tests` macro

openIssue #4299 · Chain Signatures (mpc) · pbeza

feat(attestation-cli): report which upcoming TCB evaluation data set demotes the platform

openIssue #4273 · Chain Signatures (mpc) · haiyuechen-nearone

Judge foreign chain health against the whitelist

openIssue #4271 · Chain Signatures (mpc) · anodar

Foreign TX Validation security hardening

openIssue #4270 · Chain Signatures (mpc) · netrome

Look into solutions for exporting logs from TDX nodes

investigationoperations

openIssue #4267 · Chain Signatures (mpc) · netrome

Provide script/tool to configure unattended upgrades

securityoperations

openIssue #4261 · Chain Signatures (mpc) · barakeinav1

deploy-launcher.sh: omitting `EXTERNAL_SSH_PORT` produces `--port tcp::22` and an opaque vmm-cli traceback

openIssue #4259 · Chain Signatures (mpc) · SimonRastikian

Limiting providing MeshNetworkClient to the Stores

closedPR #4247 · Chain Signatures (mpc) · SimonRastikian

refactor: redundant code extermination in running.rs

openPR #4241 · Chain Signatures (mpc) · haiyuechen-nearone

test(inspector): probe the fan out under a paused clock

openIssue #4229 · Chain Signatures (mpc) · haiyuechen-nearone

Report why a foreign chain provider's setup failed

openIssue #4225 · Chain Signatures (mpc) · haiyuechen-nearone

e2e artifacts: one predictable directory per test case containing all logs

tech-debtdevextests

openIssue #4223 · Chain Signatures (mpc) · pbeza

Pin the near-sandbox wall clock from the test environment

openIssue #4222 · Chain Signatures (mpc) · pbeza

Support controlling block time in `near-sandbox`

openIssue #4215 · Chain Signatures (mpc) · SimonRastikian

Indirect timeout in Cait-Sith

openIssue #4212 · Chain Signatures (mpc) · metalurgical

chore(dependencies): update proc-macro2 and wasm-parser

openPR #4211 · Chain Signatures (mpc) · barakeinav1

docs(tdx-guide): enable dstack-vmm on boot so it survives a reboot

openIssue #4210 · Chain Signatures (mpc) · barakeinav1

docs(tdx-guide): dstack-vmm service isn't enabled on boot — won't survive a reboot

openPR #4208 · Chain Signatures (mpc) · AmHelm

docs: added design doc for debug information service

openPR #4192 · Chain Signatures (mpc) · haiyuechen-nearone

docs: design for offchain authorization resolution (NEP-641)

openIssue #4170 · Chain Signatures (mpc) · pbeza

feat(attestation): CLI to scan TDX attestation status across a whole network

openPR #4162 · Chain Signatures (mpc) · SimonRastikian

docs: document devnet automation building blocks

openIssue #4156 · Chain Signatures (mpc) · kevindeforth

ensure prometheus node-list is in sync

openPR #4154 · Chain Signatures (mpc) · metalurgical

chore: propagate errors from assets and storage

openIssue #4153 · Chain Signatures (mpc) · gilcu3

Decide how the foreign-chain fan-out should treat provider auth failures

securityobservability

openIssue #4152 · Chain Signatures (mpc) · haiyuechen-nearone

Per-provider RTT observability for foreign-chain RPC

openPR #4146 · Chain Signatures (mpc) · SimonRastikian

refactor(scripts): extract release helpers into common.sh

Showing 30 of 537Clear filters →