Skip to content
DOCS
GIWA Sepolia
Docs/INTEGRATION GUIDES/Partner-perspective GIWA onboarding — SDK 0.3.9
GITHUB EXAMPLES / FULL GUIDE

Partner-perspective GIWA onboarding — SDK 0.3.9

On this page

An anonymous checkout of the public examples was used as a new partner application. It imported the published npm SDK 0.3.9 and the public feature helpers, deployed new partner wallets, two new tokens, a new market and a new source, and registered against the already enabled V3 standard. No new governance or per-partner Ammora approval transaction was needed. Every holder still consented and the controller still authorized registration.

PASSED_THIS_RUN: 28 successful canonical transactions, native nonces 2064–2091; final latest/pending nonce 2092. Actual native fees were 3054093350 wei, within the 50000000000000 wei task cap. Every transaction had value 0. Receipts were observed canonically with at least 13 confirmations, without a finalized-status claim or transaction resend.

Follow SELF-SERVICE.md. The machine-readable evidence binds transaction identities, results, relevant source digests and reuse scope. The earlier 76-transaction qualification remains unchanged and separate.

What the partner needed

GIWA Sepolia (91342), Node 24, the public SDK 0.3.9, native test ETH for gas, a compatible owned source, two ERC20 inventories and explicit holder/controller consent. No Ammora invitation, service API, Indexer or private protocol source checkout was used by the application. Existing installed public dependencies were REUSED after exact archive/lock/environment integrity review; this case does not claim another fresh npm installation.

The enabled standard checks implementation/runtime classes and the actual source/token/dependency graph. It does not require the old sample token or market addresses. A new implementation or token behavior still requires standard review. This conclusion is separate from native-pool token policy and ordinary permissionless launchpad Config creation.

Identity New test address
Partner A / original beneficiary 0x95979BF9661A89be9975b8669Cd8abD331cf1d1D
Partner B 0x30Bf1C2aDA019202179BF0dD0b8a5574759F016f
Quote token 0xF8A4Ac8b115d7349A86E8dFAFD5725eaAf353D9f
Base token 0x93cE816a2fE0114915CfA575A4D3f237fD19260A
Market dependency 0x4572Da5c8E154809aB300EB8b1ECD139cFd9867b
Source 0xB1A2c7ab9814E08a76E2DC31a39E1AD1A7dbf60A
Module 0x28Bea01E11e42dc3893a10Db3b323204C4Ac3b7A
Vault 0xBa7381255376aCf8891255c78F0773cf2F0282E4

Registration produced actual readyAt 1793794599 / 2026-11-04T12:16:39Z. After that boundary, fresh chain time, ticket/rights epochs, nonce, runtime, source beneficiary and exact inventory were checked before signing. Elapsed wall time was not accepted as activation proof.

Feature examples used

The public guide now connects partner:create-test-assets, partner:create-test-source, partner:configure-test-source, compatibility diagnostics, real holder consent/module deployment, partner:verify-module-deployment, direct registration/activation, partner:quote-module, partner:prepare-module-claim, cancellation and receipt-only recovery. A new unsigned configuration helper accepts the partner's own asset/dependency addresses and weighted recipients. The market deployment includes its required uint8 family constructor argument.

The public deployment-pin helper checked the known hash, chain/genesis, canonical factory event/mapping and child identities. Those exact public pins fed the actual trade/claim helpers. The application retained each genuine SDK client/plan while signing/simulating; CLI JSON was not rehydrated into executable authority. A separately controlled sender submitted the exact requests once and recorded each hash before transport completion. Frozen compiler artifacts were reused only for supplementary operator runtime verification.

Actual trades and newly secured revenue

Direction Input decrease raw Output increase raw Fee secured raw Canonical transaction
quote → base 10000 9900 100 receipt
base → quote 10000 9900 100 receipt

Each trade matched ManagedExecuted, Routed, Executed and Allocated event identities, SDK receipt reconciliation, and receipt-block balances/debt. For each newly secured 100 raw fee, Ammora received rights to 20 raw and the partner's 80 raw split 60:40 into 48/32. The checked on-chain recipient order was Partner B then A, with corresponding weights 4000/6000; each holder kept its intended share. Managed nonces 7/8 were separate from the wallet transaction nonce.

Six positive fixed-beneficiary payments

Asset Beneficiary Paid raw Exact receipt-block balance raw Canonical transaction
quote 0x13cD27a6E337097dB858C9C4FA472FbAd2F2c637 20 49900 → 49920 receipt
quote 0x95979BF9661A89be9975b8669Cd8abD331cf1d1D 48 0 → 48 receipt
quote 0x30Bf1C2aDA019202179BF0dD0b8a5574759F016f 32 0 → 32 receipt
base 0x13cD27a6E337097dB858C9C4FA472FbAd2F2c637 20 49900 → 49920 receipt
base 0x95979BF9661A89be9975b8669Cd8abD331cf1d1D 48 0 → 48 receipt
base 0x30Bf1C2aDA019202179BF0dD0b8a5574759F016f 32 0 → 32 receipt

All six official SDK planClaim calls matched Paid, ERC20 Transfer, positive beneficiary balance increases, and matching Vault debt/liability/cash decreases. A no-op, mint or planned request was not counted as a payment. These module claims are fixed to their beneficiary and do not grant arbitrary payout-address or LP delegation powers. Existing Creator/Partner and delegated LP proofs are REUSED in their original scope.

Refusals and cleanup

PASSED_THIS_RUN: five exact live-chain call refusals: early activation (TimelockPending()), registration by a rights holder who is not controller (Unauthorized()), re-registration after cancellation (Unsupported(10)), and debtless guardian claims for each new asset (InvalidRights()). No negative transaction was broadcast.

The module was stopped, the source's original new partner beneficiary restored, and the task's token allowances and Router/Module/Vault balances, debt and liability were zero. Secured and claimed amounts matched at 100 raw per asset. The existing three source inventories were unchanged. Only this task's writer lease was released and signing/sending stopped.

The new source retains 50000 raw per asset of openly mintable, valueless fixture inventory; it was not withdrawn or described as recovered principal. Both partner contract wallets share one approved physical test signer. This verifies controlled role separation, not independent production custody.

Checks and honest limits

Required gate Classification Scope
New-address partner flow and canonical deployment pins PASSED_THIS_RUN Public SDK/example application, no new governance transaction
Changed helper tests and strict types PASSED_THIS_RUN 16 distinct cases; current inventory 273 TS files / 203 commands
Public package installation, SDK/core/compiler and unchanged example proofs REUSED Same qualified archive, lock, runtime and original proof inputs
Two trades, six payments, five typed denials and cleanup PASSED_THIS_RUN This new synthetic source and assets only
Existing launchpad, Creator/Partner and LP delegation proofs REUSED Original deployments, callers, assets and canonical blocks only
Real issuer or arbitrary new implementation BLOCKED No real issuer, novel standard or independent operating review supplied
SDK publication, GitHub CI, mainnet and production NOT_APPLICABLE Not executed

Original failures remain preserved: strict tuple typing was corrected before sending; a missing market constructor family was caught by simulation before signing/broadcast, then only the corrected unsent request was submitted. The four successful deployments before that failure were reused. The 25 initial receipt/header disagreements were preserved and recovered through the same original hashes with at least 13 canonical confirmations; no successful prefix was resent. This does not establish finalized status or a particular provider/reorganization root cause.

This fixture implements synthetic ERC20 exact-input transfers with a 1% fee. It does not qualify real DEX pricing, Graduation, native-asset execution, a stablecoin issuer, arbitrary proxies/Hooks or production custody. Those are separate product/standard requirements. Relevant source/ABI/SDK/dependency, deployment/rights/epoch, input, receipt or evidence integrity changes invalidate affected reuse.

All 28 transaction identities

Native nonce Action Canonical transaction
2064 01-wallet-partnerA receipt
2065 02-wallet-partnerB receipt
2066 03-new-quote receipt
2067 04-new-base receipt
2068 05-new-market-v2 receipt
2069 06-new-source receipt
2070 07-consent-partnerA receipt
2071 08-consent-partnerB receipt
2072 09-create-module receipt
2073 10-connect-source receipt
2074 11-register-source receipt
2075 12-mint-quote-source receipt
2076 13-mint-quote-owner receipt
2077 14-mint-base-source receipt
2078 15-mint-base-owner receipt
2079 16-approve-quote receipt
2080 17-approve-base receipt
2081 18-activate-source receipt
2082 19-trade-quote receipt
2083 20-trade-base receipt
2084 21-cancel-source receipt
2085 22-claim-quote-ammora receipt
2086 23-claim-quote-partnerA receipt
2087 24-claim-quote-partnerB receipt
2088 25-claim-base-ammora receipt
2089 26-claim-base-partnerA receipt
2090 27-claim-base-partnerB receipt
2091 28-restore-source receipt
Was this page helpful?