Skip to content
DOCS
GIWA Sepolia
Docs/INTEGRATION GUIDES/GIWA self-service qualification — completed synthetic flow
GITHUB EXAMPLES / FULL GUIDE

GIWA self-service qualification — completed synthetic flow

On this page

Published SDK 0.3.9, GIWA Sepolia (chain 91342). 76 successful canonical transactions, nonces 1988–2063; final latest and pending nonce 2064. Actual native fees: 14,535,538,337 wei, below the 125,000,000,000,000 wei task cap. Every transaction had value0. No SDK publication, GitHub CI, mainnet or production change occurred.

Two reusable synthetic standards remain enabled. Three independently configured source modules were registered directly by their controller, activated after their actual tickets, traded and paid fees, then deliberately stopped for cleanup. Live registration/trading targeted stage 1 (pool). A new partner creates its own conforming source; these stopped test modules are not reusable live trading targets. A real issuer, source implementation and independent review have not been selected.

Required boundary Classification Actual scope
Public package/default install, SDK/core/compiler proof REUSED Same qualified 0.3.9 archive/runtime, frozen artifacts and 41 transitive source inputs; original scope retained
Existing Creator/Partner/multiple-recipient and LP delegation payouts REUSED Original canonical receipts, authority and exact-block payments; no new LP transaction
Example and extraction interfaces REUSED Ten example and six extraction cases, root types,267 TS/198 commands; executable/test/dependency inputs unchanged
Deployment/runtime and holder consents PASSED_THIS_RUN Exact full runtimes, factory mappings and consent for all 3 Source/Port/Vault instances
Bootstrap and standards PASSED_THIS_RUN Two common templates enabled after genuine serial 3600-second gates
Compatibility and direct registration PASSED_THIS_RUN Three compatible sources, eight unsupported cases; same V3 standard reused twice, no per-instance governance call
SDK activation and recovery PASSED_THIS_RUN Three actual activations after their third real delay; genuine local plans and observed receipt-only recovery, mayResubmit=false
Managed exact-input trades PASSED_THIS_RUN Six trades, both directions across 3 modules;10,000 raw input,9,900 raw output,100 raw newly secured fee each
Fixed-beneficiary payments PASSED_THIS_RUN Twelve official SDK planClaim sends;20 raw Ammora and 80 raw partner per asset/module, Paid/Transfer and receipt-block balance increases
Authority and stopped-state refusals PASSED_THIS_RUN Earlier two waiting/wrong-controller refusals plus six stopped/debtless-holder refusals; no negative broadcasts
Final cleanup and signer handoff PASSED_THIS_RUN Three test modules stopped, source beneficiaries restored, all task allowances and Router/Port/Vault cash/debt/liability 0; own writer lease released
Real issuer/production standard BLOCKED Source/dependencies/token behavior, actual rights, independent review and operating acceptance not supplied
SDK republication, GitHub CI, mainnet, production NOT_APPLICABLE Excluded and not executed

Registration and activation

Source Module Actual ticket readyAt Unix Activation
sourceV3A 0x357295bda8D847e3Be59f1a2cD0E3A7555c65bAc 1793781401 receipt
sourceV3B 0x64B7Eb4e601E0fa365cb3478a5817a56B4Eb89cf 1793781445 receipt
sourceV4 0x3F5735c0E2C525e98267db0D16b03eEc9667be44 1793781489 receipt

The final ticket readyAt was 2026-11-04T08:38:09Z. Fresh chain-time, epochs, nonce, runtime and inventory checks preceded signing. Elapsed wall time alone was never accepted. Governance, guardian and partner are different controlled contract role addresses, but share one physical test signer; this is not independent production custody. Registration, activation and cancellation retained genuine SDK plan/client authority and used receipt-only recovery after submission.

Six actual managed trades

Source Input asset Owner input decrease raw Owner output increase raw Newly secured fee raw Receipt
sourceV3A quote 10000 9900 100 receipt
sourceV3A base 10000 9900 100 receipt
sourceV3B quote 10000 9900 100 receipt
sourceV3B base 10000 9900 100 receipt
sourceV4 quote 10000 9900 100 receipt
sourceV4 base 10000 9900 100 receipt

Actual ManagedExecuted/Routed/Executed/Allocated receipt evidence and exact-block input/output, secured fee and 20:80 debt changes were checked. Native flags were false: the quote fixture is not WETH. No mint, observation-only receipt or zero-fee no-op was counted as revenue payment.

Twelve positive fixed-beneficiary payments

Module Asset Beneficiary Amount raw Balance before raw Balance after raw Receipt
sourceV3A quote Ammora EOA 20 29700 29720 receipt
sourceV3A quote Controlled partner holder 80 0 80 receipt
sourceV3A base Ammora EOA 20 29700 29720 receipt
sourceV3A base Controlled partner holder 80 0 80 receipt
sourceV3B quote Ammora EOA 20 29720 29740 receipt
sourceV3B quote Controlled partner holder 80 80 160 receipt
sourceV3B base Ammora EOA 20 29720 29740 receipt
sourceV3B base Controlled partner holder 80 80 160 receipt
sourceV4 quote Ammora EOA 20 29740 29760 receipt
sourceV4 quote Controlled partner holder 80 160 240 receipt
sourceV4 base Ammora EOA 20 29740 29760 receipt
sourceV4 base Controlled partner holder 80 160 240 receipt

Every payment used official SDK 0.3.9 createPartnerExtensionClientV2.planClaim, matched the frozen Vault ABI exactly and required a positive Paid event, matching ERC20 Transfer, receipt-1/receipt-block recipient balance increase, and matching debt/liability decrease. The controlled contract holder used its reviewed outer execute call. Claims remained payable after cancellation/guardian stop. These are fixed-beneficiary rights, not arbitrary payout-address or LP delegation powers; the latter products retain their separate REUSED proofs.

Refusals and final cleanup

Actual early activation returned TimelockPending; an outer guardian attempting controller registration returned Unauthorized. After two controller cancellations and one guardian stop, all 3 modules rejected re-registration with exact Unsupported(10). A debtless guardian could not take partner fees (InvalidRights). Refusals used real outer-actor eth_call simulations; no contract was impersonated as an EOA and no failed test transaction was broadcast.

Final canonical state has no pending task nonce, zero owner-to-Router allowances, zero Router/Port/Vault cash, zero task internal allowances, zero vault liability/debt/pass-through/unattributed balances, and zero module claimable at each source. Each module/asset secured and paid 100 raw. Original source beneficiaries were restored. The task's own writer lease was released and signing/sending stopped.

Each source still holds 50,000 raw quote and 50,000 raw base; total 150,000 raw per asset. These openly mintable assets are valueless inventory in a fixture with no withdrawal method. This is not withdrawn principal, issuer reserves or money recovered. Synthetic1:1 exact-input / 1% fee behavior does not certify actual DEX pricing, Graduation, exact-output, arbitrary proxies/Hooks/tokens, issuer support or an independent audit.

Preserved failures and reuse

The initial standalone Registry metadata mismatch and one-code-store assumption were recovered read-only against the original successful hashes, requiring every exact embedded/runtime byte. No resend, redeploy, metadata mask or verifier bypass occurred. Original type-only/runtime-identity and private preparation failures remain preserved; unchanged failed commands were not automatically retried.

Initial receipt/header hashes disagreed for 66 of 76 transactions. Bounded same-hash observation required a matching canonical block and 13 confirmations, retaining all originals with zero resends. This is observed canonical inclusion, not finalized status; the evidence does not assign caching versus reorg causes. Transport dispatch counts are not account billing.

Relevant source/ABI/compiler/artifact, SDK/dependency, chain/genesis/runtime, role/rights/epoch, canonical receipt or preserved-evidence changes invalidate affected reuse. Old fee/LP and SDK tests retain their original asset/authority scope. Main integration is separately established by the linked PR's merge metadata; passing this synthetic flow is not whole-service or real-partner certification. No production or Docs deployment is included.

Was this page helpful?