Skip to content
DOCS
GIWA Sepolia
Docs/INTEGRATION GUIDES/Fresh partner execution — public SDK 0.3.9
GITHUB EXAMPLES / FULL GUIDE

Fresh partner execution — public SDK 0.3.9

On this page

On 2026-11-05 KST, a new anonymous source project exercised the public partner onboarding instructions and product guides. Start new integrations with the English partner quickstart. Public npm SDK 0.3.9 ran against GIWA Sepolia (91342) without a customer invitation or per-Config Ammora approval. Actual writes used an explicitly approved, controlled test wallet and a durable signer journal. This is a controlled partner-role test, not qualification of a real issuer or independent custody.

The supported launchpad/agent lifecycle completed 18 unique canonical successful transactions, nonces 2092–2109. Final latest and pending nonce were 2110. Creator/Partner FeeVault and two LP claims matched payment events, token Transfers and exact receipt-block balance increases. No public SDK or executable-example change was needed.

Product-by-product result

Product Newly executed in this project Reused evidence and limits
Launchpad Deployment/Explorer gate, Config list/read, new Config #25, token issuance, curve buy/sell, terminal partial fill, Graduation, pool buy/sell Existing atomic first-buy and other unchanged Config variants retain their original receipts.
Agent Tool schemas, keyless live smoke, public connectAgent + runLaunchpadWalkthrough + reviewed per-step execution, allowance prerequisites and durable receipt reconciliation A trusted host supplies its own signer, policy and owner review. Installing tools grants no signing rights.
Fee sharing Config preview/state; real own WETH and new-token FeeVault payouts; real LP #35/#37 payouts; foreign FeeVault/LP caller refusals Existing distinct-wallet Creator/Partner/multi-recipient and fee-only LP delegation, separate-payee and revocation proofs are REUSED. Current role addresses share one physical signer.
Issued stablecoin pool Actual unified policy and discover CLI against reviewed synthetic 18/6-decimal assets and explicit giwa-almm-unified-v1 profile Prior synthetic pool/LP/swaps/delegated payouts/denials/exit are REUSED, not sent again. This does not certify FDUSD, cUSD, USDT, a peg or a live price oracle.
External revenue Actual partner:standards CLI and enabled-standard discovery Prior fresh nongovernance partner registration, actual delayed activation, two trades, six positive 20:48:32 payments, typed refusals and cleanup are REUSED. Completed modules remain stopped. Arbitrary source implementations still need review.
Token vesting Actual offline allocation and live inspection of the documented completed public lock Existing supported creation/claim evidence is REUSED. The completed lock has zero claimable and supplies no new payment to a new partner.

All ten documented keyless commands and both unified stablecoin planner commands exited successfully. quickstart:verify checked 30 deployed contracts, including Explorer source verification. A separate exact public Config call simulated successfully from a nongovernance public address; this was an unsigned simulation, not a new persisted Config from that address.

New launch and positive payments

  • Config: 25
  • Token: 0xeFD0b74cB733534D6554894c0FdF5931a711BCFB (KGPT, 9 decimals)
  • Curve: 0xCc803Eb81b7Cf3a71dBF17d25E342e45F17be209
  • Graduated pool: 0xD912Fa18061E5665136AE5dBc002aDa0fc0D3c28
  • Position manager: 0x089163706d9956d7baeCeDF4eAb4aD6CcE7Ca2D6
Claim Transaction Exact recipient increase (raw)
claim-own-quote 0xd53386a278eacc29c4cf0f43c81898bf30ea9c2cc4dfd973c62174e6e2c3db49 0x4200000000000000000000000000000000000006: 7232101895479
claim-own-base 0xaacaf278dfcd58f3ecc9bdfe7255d60f6fc9c2799aefc623bc5c7d98857ca23d 0xeFD0b74cB733534D6554894c0FdF5931a711BCFB: 20408163
claim-lp 0xe99284ddf00ea057c51c1442a406e2459e4318d230bc66edc6304038ad429993 0xeFD0b74cB733534D6554894c0FdF5931a711BCFB: 49999; 0x4200000000000000000000000000000000000006: 4999999
extra-lp-37 0xcff24c987fc1ff3a37d6907aaa2d09f17b9d6a8715909c53366d4356c5328ef3 0xeFD0b74cB733534D6554894c0FdF5931a711BCFB: 29999; 0x4200000000000000000000000000000000000006: 2999999

FeeVault WETH is aggregate beneficiary/token revenue, not per-launch revenue. Both Creator and Partner were the same controlled wallet in this new run. Separate-payee/delegated evidence is reused within its original actor/asset/receipt scope. LP #36 had zero accrued fees: no signature or transaction was made, and it is NOT_APPLICABLE as a payment.

Current-chain eth_call controls confirmed Unauthorized for redirecting a foreign FeeVault beneficiary and InvalidPermission for a foreign caller on the new LP. Authorized control calls succeeded. These are simulations, not reverted transactions or payouts.

Transactions

Receipts were independently checked against their canonical headers, original hashes/nonces and at least 13 confirmations. This is not a finalized-status claim. Terminal partial-fill unused ERC20 input stayed in the payer wallet; it was not a refund payment.

Cleanup and retained inventory

All four task-specific WETH/KGPT allowances to the new curve/pool are zero. Only the unused new-curve allowance required a zero-approval transaction. The own writer lease was released after final canonical/nonce reconciliation; signing and sending stopped. Legacy approvals and other teams’ assets/recipients were unchanged.

New LP NFTs #35 and #37 retain permanent liquidity; #36 retains one raw unit of unlocked dust. No permanent principal was withdrawn or lock ratio changed. The new Config/token/curve/pool and remaining owned test-token inventory persist. The machine-readable snapshot below records exact liquidity and balances, not a claim that every wallet allowance or all assets are empty.

The 18 raw receipts report 1603966415 wei execution gas plus 3498 wei explicit L1 fees = 1603969913 wei total recorded native fees, below the 250000000000000 wei task cap. Reserved gas envelopes are not actual fees or account billing.

Evidence classification and preserved failures

  • PASSED_THIS_RUN: anonymous fresh installation, documented read/plan examples, new connected lifecycle and positive payout proofs, current refusal controls, final hash/nonce/receipt reconciliation and task-only approval cleanup.
  • REUSED: unchanged SDK/helper/type/compiler and prior financial evidence listed in the product table after digest/component checks. 334 executable/config/dependency files matched the preceding qualified source; 180 documentation delivery files, 24 SDK release-delivery files and 535 partner evidence leaf files matched their preserved digests.
  • BLOCKED: no unresolved gate for this controlled supported-path run. A real issuer’s unconfirmed assets, unsupported standards/implementations, restricted policies or missing partner authority/funding remain separate prerequisites; this report does not qualify them.
  • WAIVED: none.
  • NOT_APPLICABLE: zero-fee LP #36 payment; SDK publication, GitHub CI, mainnet and API/Indexer/production changes.

Original failures remain preserved: the first private host gas cap rejected before keys/signatures; the host cap was corrected for the actual SDK gas-price formula with the total budget unchanged. Two private Config-simulation invocations used the wrong pure-helper arguments and were corrected. One restricted-network extra-LP attempt failed before signing and resumed with network access under the same request IDs. A historical integrity map referenced an earlier digest of its own seal; that self-reference was not qualified, while all 535 financial evidence leaf digests matched. Temporary canonical-block lookup failures reconciled the original hashes; no known successful or uncertain hash was resent. None required an SDK change.

Reopen affected evidence when relevant SDK/source/dependency/runtime/profile, inputs, caller/rights, asset or canonical receipt identity changes, or when a preserved digest no longer matches. Reused proof never authorizes a different partner’s transaction.

Source and machine-readable evidence

Main integration and public Docs delivery are tracked separately from these chain results. This report does not certify the whole service, public app visibility, real-issuer onboarding or mainnet readiness.

Was this page helpful?