Skip to content

chore(backend): horizen testnet wipe script + e2e fixes#275

Merged
gianalarcon merged 2 commits into
developfrom
chore/horizen-testnet-cleanup
May 21, 2026
Merged

chore(backend): horizen testnet wipe script + e2e fixes#275
gianalarcon merged 2 commits into
developfrom
chore/horizen-testnet-cleanup

Conversation

@Huygon764
Copy link
Copy Markdown
Contributor

No description provided.

Huygon764 added 2 commits May 21, 2026 11:43
… require

- Add scripts/wipe-horizen-testnet.ts (yarn wipe:horizen-testnet) to drop
  all chainId 2651420 accounts + their transactions/votes/signers/contacts
  /reserved-nonces. Used after the Horizen testnet zkVerify address swap
  to clear stale state on staging. Safety: refuses when APP_NETWORK=mainnet,
  unlinks batch_items.contactId before cascading account deletes,
  --dry-run prints counts without touching data.

- Pass chainId in e2e + staging-e2e test utilities for reserveNonce and
  createTransaction calls. The endpoints started requiring chainId after
  the (address, chainId) account key rollout; the tests still sent the
  legacy shape and got 400.

- stagingExecuteTransaction: fall back to polling GET /transactions/:txId
  when the initial POST hangs up (socket reset by edge / proxy idle
  timeout) instead of bubbling a cryptic ECONNRESET. Server already
  persists txHash right after on-chain submission so the poll is safe.
@gianalarcon gianalarcon merged commit 2fbdc1a into develop May 21, 2026
2 checks passed
Huygon764 added a commit that referenced this pull request May 22, 2026
* fix(zkverify): update Horizen testnet zkVerify contract address (#274)

* chore(backend): horizen testnet wipe script + e2e fixes (#275)

* chore(backend): horizen testnet wipe script + e2e fixes after chainId require

- Add scripts/wipe-horizen-testnet.ts (yarn wipe:horizen-testnet) to drop
  all chainId 2651420 accounts + their transactions/votes/signers/contacts
  /reserved-nonces. Used after the Horizen testnet zkVerify address swap
  to clear stale state on staging. Safety: refuses when APP_NETWORK=mainnet,
  unlinks batch_items.contactId before cascading account deletes,
  --dry-run prints counts without touching data.

- Pass chainId in e2e + staging-e2e test utilities for reserveNonce and
  createTransaction calls. The endpoints started requiring chainId after
  the (address, chainId) account key rollout; the tests still sent the
  legacy shape and got 400.

- stagingExecuteTransaction: fall back to polling GET /transactions/:txId
  when the initial POST hangs up (socket reset by edge / proxy idle
  timeout) instead of bubbling a cryptic ECONNRESET. Server already
  persists txHash right after on-chain submission so the poll is safe.

* chore(docker): include backend scripts/ in runner image for Cloud Run Jobs

* fix(docker): copy src/generated/prisma into runner for tsx scripts (#276)

* feat(nextjs): allow creating accounts with a single signer (1-of-1) (#277)

* refactor(nextjs): dedupe shared utils and split batch contacts modal (#278)

* refactor(nextjs): dedupe shared utils and split batch contacts modal

- Reuse formatAddress/formatCommitment for address/commitment truncation
- Fix copyToClipboard (copy then notify, error on unavailable) and unify call sites
- Add notifyError helper; replace 17 inline error notifications
- Add useTokenResolver hook; drop duplicated getTokenByAddress wrappers
- Extract createFormControl factory shared by FormInput/FormTextarea
- Split 763-line CreateBatchFromContactsModal into step components + types

* docs: fix outdated setup, schema, API and ZK details

- getting-started: Node >=20.18.3, remove duplicate clone keyword
- database-connection-guide: 18 tables with full list, drop nonexistent users.name column
- api-documentation: remove unimplemented PATCH /users/me
- zero-knowledge-implementation: correct identity message to noir-identity

---------

Co-authored-by: GianM <gian@quantum3labs.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants