bos-auth: 02 gasless wallet publish — bos publish --wallet via NEP-366 relayer

Open
#289 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend-api-design, blockchain, cli

Research direction

Start with the wallet/session surface from #288, then trace the existing bos publish key-based flow and ephemeral relayer configuration. Map where the FastKV config and deploy manifest writes are assembled, and verify the acceptance criteria: one wallet approval, atomic writes, confirmation payload equality, sized relayer limits, and unchanged NEAR_PRIVATE_KEY behavior.

Written by the indexing model from the issue text.

Description

ready-for-agent

Sprout of #274 (v2 platform services spec); mirrors #282 (gasless publish) with the deploy-service write-back chain decoupled. Built after #288 so the wallet/session surface exists.

What to build

bos publish --wallet submits the FastKV config write as a gasless NEP-366 delegate action through the existing ephemeral relayer:

  1. Whitelist the FastKV registry contract in the relayer config and size gas/deposit for ~10 KB config writes.
  2. Build the delegate action for set_values of the config key and the per-deploy manifest key atomically in one transaction — the on-chain ledger mirror of the deploy-service records rides the same write.
  3. Confirmation loop re-reads the registry and verifies payload equality (same semantics as the current key-based publish flow).
  4. The existing local-key publish path stays byte-compatible for CI/agents — --wallet is additive, never a replacement.

Acceptance criteria

  • A human publishes a config to testnet FastKV with one wallet approval and zero locally-stored keys
  • The relayer whitelist covers the FastKV registry contract with sized gas/deposit limits
  • Config key + deploy manifest key are written atomically
  • Confirmation re-read verifies payload equality
  • The existing NEAR_PRIVATE_KEY publish path still works unchanged
  • Failure leaves no partial on-chain state (atomic delegate action)

Blocked by

  • #288 (bos login — the wallet/session surface)
Dominant language
TypeScript
Stars
5
Forks
6
Avg merge
1m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NEARBuilders/everything-dev

All issues in NEARBuilders/everything-dev

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.