Guppy's Guide — Don't Panic

Transparency Report — CAW (Ethereum Edition)

Everything about the community deployment of the Gilgamesh-designed CAW protocol on Ethereum, Base and Arbitrum: what was deployed, which admin rights were renounced or locked, what powers remain by design, where the money went, and every correction made along the way. This report is updated by appending; past entries are not silently edited.

How to read this report

Two kinds of statements appear here, and they are kept separate. Facts enforced by the contracts (ownership renounced to the zero address; fees and ownership changes locked on-chain) can be verified by anyone, and transaction links are given. The destruction of the deployer key is the operator's declaration: it is an operational act that cannot be proven on-chain. An inactive address proves only that it has not been used — not that its key was destroyed. We do not blur this line.

1. What was deployed

2. The two deployments, labeled

Two deployments of the same code exist on-chain. The first was deployed and then rebuilt on November 11, 2026 for one reason: its first minted name was the test name "guppytest", and name numbers cannot be changed afterwards — the initiator wanted #1 elonmusk and #2 donaldtrump (the same opening pair as the QL1-side CAW). The first deployment was never opened for general use; it was discarded and then closed the same day (section 3). The app, the node kit and the node registry connect only to the current deployment. Names and deposits do not carry over between deployments.

ContractFirst deployment (discarded · closed)Current deployment
CawProfile (Ethereum)0x82455d1a90DD177F02a9b9d0f115Ce30e224DCE30xa3700808e1c62E989fbf5CE15312d79d1475bDb4
CawProfileMinter (Ethereum)0xA19EC9Dc81fff2b8f254230EB8603ee56D0fF5680xf219DA7aF9249322D4E982dc49FcE6251bCE0d22
CawProfileQuoter (Ethereum)0x01fDbc549Caaa9585c931f114A6cC323944f0BE40x4baBf4136707d6f4C096ea447Ec3285Cc2AF7235
CawNetworkManager (Ethereum)0x09Ee733Eb6BA19dEBC0E576AA18333A9A5A6D5460x426C22504fd710fbAEAcd0c15e7aad80210a1E12
CawActions (Base)0xE03a95A5f1681c80D9308A4E571cE9Ee8977F3260xf4dFCf0EF472E8aaD3783479051f61EC574C6A8E
CawProfileLedger (Base)0x595a4413797Eba8dCA76F37A8f6635B22Bf378E50x206c99Ee5CFF8b5D761926ff224D867E1fBC7aaa
PathwayExpander (Ethereum)0x29225D1177d0ECB3C0309417197D493b827A75b00xCdbDd8533e8E287F378687Aa70208FfCfF997D39
PathwayExpander (Base)0x29225D1177d0ECB3C0309417197D493b827A75b00xd14C3038141C849612825760D9832515323462B5
PathwayExpander (Arbitrum)0xc41aFf35C236f24404283ee909A2d0641E44fa420xdAD5bac641ABe10A11188A1AED7fAd282188A76a

The CAW token itself is pre-existing and shared by both deployments: 0xf3b9569F82B18aEf890De263B84189bd33EBe452. The full list of all 33 deployed contracts for each deployment is in the appendix at the end of this report.

3. Admin rights: renounced, locked, and one exception

Renounced (contract-enforced fact)

Locked (contract-enforced fact)

The one exception

Babylon's authentication fee of 0.00025 ETH remains — in both deployments — and is itself permanently locked. Network fees are charged at twice the configured value by design (half to the fee recipient, half to the protocol's BuyAndBurn pool), so one Babylon authentication costs 0.0005 ETH in total. Zeroing this last fee would have required an extra cross-chain broadcast step; instead it was frozen as-is and is disclosed here rather than rounded down to "zero fees".

4. Residual powers, and the key

The protocol design keeps a per-network owner role inside CawNetworkManager, and the code provides no function to renounce it. In both deployments that role is recorded as the deployer address 0x41652120aE1D605AFFF4beAcd3A1cc0E22C7FF64 — a throwaway key created for the deployment work, never a personal wallet. After the locks, exactly two powers remain attached to that role, by design:

On November 11, 2026, after both deployments were closed or locked and all remaining funds were returned, every copy of the deployer private key held by the operator was destroyed. On that basis, the two residual powers cannot be exercised by anyone, and the accrued fees in section 5 can never be released. As stated at the top of this report: the destruction is a declaration. What anyone can verify is the on-chain state — the renouncements, the locks, and an address that stays inactive.

⚠️ Never send funds to the deployer address 0x41652120aE1D605AFFF4beAcd3A1cc0E22C7FF64. No one can ever operate it again; anything sent there is lost permanently.

5. Money: fees, refunds, and what the operator holds

6. Names issued

DeploymentNameOwnerDepositNote
Current#1 elonmusk0xDa80dd4B3071B7c4f925405606B6aE535B0689DC1,000,000 CAWGenesis name, minted by the operator at the initiator's instruction and transferred to the initiator's admin wallet
Current#2 donaldtrump0xDa80dd4B3071B7c4f925405606B6aE535B0689DC1,000,000 CAWSame as above
Current#3 guppy0xe32e4807666355e7626b70736053017790488CaB1,000,000 CAWThe initiator's own name, minted by himself in the app (burn cost 200,000,000 CAW for 5 characters)
First (closed)#1 guppytest0x98A8e75DA31Dc23b65c31FFB1F11d28f61cE0E7a1,000,000 CAWTest name. Its owner is a throwaway wallet whose key was also destroyed — the name and deposit can never be moved or withdrawn

Each name's deposit is withdrawable by its owner through the protocol (none of the three current names carries a withdraw lock — verified on-chain). Deposits sit in the name's ledger balance on Base and return over LayerZero when withdrawn.

7. Correction log

Mistakes we made in describing this deployment, and what was corrected. Kept here permanently.

Nov 11, 2026 — evening
"All admin rights renounced / no admin remains" was too broad. Our renouncement check covered contract-level ownership (PathwayExpander) but missed the per-network owner role inside CawNetworkManager. A community reviewer (ten@crypto) found it. The role was then closed as far as the code allows: fees zeroed, fee/ownership changes locked, and the key later destroyed. All public wording was corrected the same day.
Nov 11, 2026 — evening
Fee unit error. The Babylon authentication fee was described in places as "0.00025 CAW". The fees are charged in ETH from the transaction value (verified in the CawProfile source): the correct figure is 0.00025 ETH. A second reviewer (RAZ13L) had the unit right; our earlier statements were wrong and have been corrected on every surface.
Nov 11, 2026 — night
The Babylon exception now covers both deployments explicitly. The fee exception was first written for the current deployment only; the first deployment carries the same locked exception, and the disclosure now says so in both places it matters (pointed out by RAZ13L).
Nov 11, 2026 — night
This report. At the reviewers' request, the two deployments are now labeled side by side (section 2), and the distinction between contract-enforced facts and the key-destruction declaration is applied uniformly across the intro site, the dashboard (Pages and Space versions), and this report.
Nov 11, 2026 — night
Accrued-fees figure corrected, and an appendix added. The first edition of section 5 counted only the half of the accrued fees credited to the fee recipient (0.0015 ETH). Read directly on-chain, the BuyAndBurn pool holds a matching 0.0015 ETH, so the amount frozen in the current deployment is 0.003 ETH in total; the first deployment holds 0.0005 ETH on each side. Section 5 now states the full amounts, and the same figure has been corrected on the intro site and the dashboard. Section 2 also pointed to deployment records that were not actually linked — an appendix listing all 33 contracts of both deployments has been added at the end of this report.
Nov 12, 2026
Node plan changed. Section 8 previously said the initiator was preparing to run the first public node on a home PC at no cost. On Nov 12 the plan changed: the first public node will be run on a VPS (in preparation, not yet online). Section 8 has been updated to match. Nothing else in this report is affected.
Nov 12, 2026 — evening
First public node live; section 8 updated. The first public node went live on the initiator's VPS on the evening of Nov 12, and the first posts (by @guppy) landed on-chain through it: first post, second post. Section 8's "no public node is running yet" was therefore stale and has been updated. One node run by the initiator is a first node, not decentralization; anyone can run the second.
Nov 12, 2026 — evening
Node client patches disclosed. Bringing the node live required two patches to the upstream NODE CLIENT (the contracts are unmodified and untouched): (1) the client's validator submit path is hardcoded to the Base Sepolia testnet chain id (84532), so an unmodified client cannot submit any mainnet transaction — the node's copy uses the Base mainnet id (8453) at the submit sites; (2) the operator's node runs in "subsidy mode": the protocol's default tip (1,000 CAW) is worth roughly 0.001 JPY at the CAW price observed on Nov 12, while one delivery costs roughly 0.36 JPY, so the client's tip-versus-cost check declines nearly every submission by design. The operator's node has that one check disabled and absorbs the difference (about 0.36 JPY per post). Posters still pay the full protocol amounts, which the contracts enforce; other nodes are unaffected and remain free to decline. The node kit now ships both patches as disclosed, fail-closed steps — the chain-id fix always, the subsidy mode as an operator opt-in that defaults to OFF — and pins the node source to an exact, verified commit so any operator installs the same reviewed code.
Nov 12, 2026 — evening
Name minting from the app reopened. The mint-enabled build (v0.1.16-pvt) became the current public release on Nov 12, superseding v0.1.16 as "latest"; the intro site, this report (section 8) and the dashboard have been updated from "under maintenance" to "reopened". The contract mint function was never halted — only the app's entrance was closed, and it is open again.
Nov 12, 2026 — evening (later)
The "-pvt" label was retired the same evening. The mint-enabled edition had begun as a private build and still carried that label when it became the latest release. Since the edition is public, the label was removed: v0.1.17 (same app, minting open in the standard build) replaced it as the current release, and the v0.1.16-pvt release was deleted.
Nov 12, 2026 — evening (later)
Summary-line shorthand corrected for consistency. A follow-up community review asked that the corrections accepted in PR #1 be applied consistently to every published claim. The long texts were already precise; the short summary lines still used the shorthand "admin rights renounced and locked". Those lines — this report's and the intro site's descriptions, and the Guppy's Guide dashboard cards (12 languages) — now state the split precisely: PathwayExpander ownership renounced; network fees locked; the per-network owner role remains recorded, and that its residual powers cannot be exercised rests on the operator's declaration that the key was destroyed. Nothing about the underlying facts changed.
Nov 13, 2026 — early hours
App UI overhaul started (a status note, not a correction). The apps of both CAW editions — this Ethereum edition and the QL1 edition — are being fully redesigned in the style of X (formerly Twitter), after a community request the initiator agreed to publicly. The overhaul changes the display layer only; signing and posting logic are untouched. Its builds are private for now, and the public release remains v0.1.17 until a separate release decision. Nothing about the contracts, authority or funds changes.
Nov 13, 2026 — afternoon
App v0.4.0 released publicly (a status note, not a correction). The X-style UI overhaul recorded above shipped on Nov 13, 2026 as app v0.4.0 and is now the public download. The rebuilt UI follows the same form as the QL1 CAW app — four bottom tabs (Home / Search / Notifications / Profile), an X-style drawer, a MetaMask-style wallet screen and a share button — while the app's signing and sending logic is unchanged, and the node connection status display stays in the header. Statements on the intro site, the Guppy's Guide dashboard and the links hub that described the overhaul as private and the public release as v0.1.17 have been updated the same day. Nothing about the contracts, authority or funds changes.
Nov 13, 2026 — evening (second audit)
Wording fix in section 8. Section 8 said the two node-client patches are recorded in the correction log "below"; the log is section 7, which sits above section 8. The sentence now says "above". This corrects a pointer inside this report's own text only — no statement about the deployment, authority or funds changes. With this entry the report becomes v1.9.
Nov 17, 2026
First public node's operation ended; section 8 updated. By the operator's decision, the first public node on the initiator's VPS ended its operation on Nov 17, 2026: the node services were stopped and disabled, and the node's data is kept on the server, not deleted. Nothing on-chain changes — the contracts, names and posts of both deployments are untouched, and the apps, the web viewer and the sites continue as before. What changes is only that no public node is running right now: reading and posting through a node resume whenever anyone runs one, and the node kit and operator guide remain published for that purpose. The static node list on the intro site has been emptied so the app and viewer no longer point at the stopped node. Section 8's Nodes line has been updated to match. With this entry the report becomes v2.0.

8. Current status, known limits, and how to verify

Appendix — all contracts, both deployments

Every contract deployed for each deployment (33 per deployment, from the deployment records), plus the pre-existing CAW token. All 33 are verified on Sourcify with an exact bytecode match. Suffixes in the deployment records: no suffix / _L1 = Ethereum, _L2 = Base, _L2b = Arbitrum.

ContractChainFirst deploymentCurrent deployment
CawActionsERC1271_L1Ethereum0xa9767fAAcF6f4CE720a910590252ee31e20EE8690x9c0331CDC003453730B19f52a507373EF0a9e513
CawActions_L1Ethereum0x32476808c5c613860F78e0B17c1101964482e1dF0x4Df413760cd196D28818478278f7A0E8b6Ee6e39
CawBuyAndBurnEthereum0xE919cA86a02016251BF8139B5abb40BDa50Ab1950xb6F3a337F318AFE16C6e952915796559e180ECAc
CawCapOracle_L1Ethereum0xa5dA10B12B866513ec593F8fee4C4D90e592a62F0xd59f55156Da7036DF3163533472107d6498c318e
CawFontDataAEthereum0x595a4413797Eba8dCA76F37A8f6635B22Bf378E50xF105C02f1Cf8Ea2C607558314b9BD35B5F187B04
CawFontDataBEthereum0xb1589314B79BBE6e9c47d9641149795Db2adb9390x8969ceD02E7B38b20256bC6341174d1ea04F4AEe
CawNetworkManagerEthereum0x09Ee733Eb6BA19dEBC0E576AA18333A9A5A6D5460x426C22504fd710fbAEAcd0c15e7aad80210a1E12
CawProfileEthereum0x82455d1a90DD177F02a9b9d0f115Ce30e224DCE30xa3700808e1c62E989fbf5CE15312d79d1475bDb4
CawProfileLedger_L1Ethereum0x387920202EB0468615B419a620d0acf189de66060x3f6E2cc5a2E7CB6984f94c826717B71FB001dD3C
CawProfileLensEthereum0x42a1BB0120deAaeCc165cc800dB4d6Ee67B231dB0x149DD52f6e2331bDfe400f08D489582C72712fcE
CawProfileMarketplaceEthereum0x8E945f8948C6D7D1259aCA158Bcec8C104bdb6730xD76B5Aa960da00B1df69eD96a4F3D6D311Ef4bd9
CawProfileMinterEthereum0xA19EC9Dc81fff2b8f254230EB8603ee56D0fF5680xf219DA7aF9249322D4E982dc49FcE6251bCE0d22
CawProfileQuoterEthereum0x01fDbc549Caaa9585c931f114A6cC323944f0BE40x4baBf4136707d6f4C096ea447Ec3285Cc2AF7235
CawProfileURIEthereum0xE03a95A5f1681c80D9308A4E571cE9Ee8977F3260xCF7e846D31193427458282eB4E3D3D348B79F1DF
MintableCaw (CAW token — pre-existing, shared)Ethereum0xf3b9569F82B18aEf890De263B84189bd33EBe4520xf3b9569F82B18aEf890De263B84189bd33EBe452
PathwayExpander_L1Ethereum0x29225D1177d0ECB3C0309417197D493b827A75b00xCdbDd8533e8E287F378687Aa70208FfCfF997D39
SessionMessageParser_L1Ethereum0x27dBE57Df5dCA071AbA7e7Dddd1a988a8C8Cd45f0xf986feF3b33c01ebA2c2D2507D2Fe7dB7882cA14
SmartEOAEthereum0x1a32DfE9e682283D0B00C6013691D1f220C25AEd0xC91a8eA79DCee6742AA125C11f3e6d37979BC992
CawActionsArchive_L2Base0x09Ee733Eb6BA19dEBC0E576AA18333A9A5A6D5460x9ac02C514A016c7E6A92cf69a44a4d793b6b9cfE
CawActionsERC1271_L2Base0xE919cA86a02016251BF8139B5abb40BDa50Ab1950x1aF9fc193d23528C9F8C17030Bf3A61C5473d52c
CawActions_L2Base0xE03a95A5f1681c80D9308A4E571cE9Ee8977F3260xf4dFCf0EF472E8aaD3783479051f61EC574C6A8E
CawCapOracle_L2Base0xb1589314B79BBE6e9c47d9641149795Db2adb9390x31e8F103F717C48c5FA6c9b9134a2AD1aEe8b1aE
CawChallengeRelay_L2Base0x27dBE57Df5dCA071AbA7e7Dddd1a988a8C8Cd45f0x747B7Bc621f3705e4Cd84eF0f94F2C1fF335F611
CawProfileLedger_L2Base0x595a4413797Eba8dCA76F37A8f6635B22Bf378E50x206c99Ee5CFF8b5D761926ff224D867E1fBC7aaa
PathwayExpander_L2Base0x29225D1177d0ECB3C0309417197D493b827A75b00xd14C3038141C849612825760D9832515323462B5
SessionMessageParser_L2Base0xc41aFf35C236f24404283ee909A2d0641E44fa420xdAD5bac641ABe10A11188A1AED7fAd282188A76a
CawActionsArchive_L2bArbitrum0xE919cA86a02016251BF8139B5abb40BDa50Ab1950x1aF9fc193d23528C9F8C17030Bf3A61C5473d52c
CawActionsERC1271_L2bArbitrum0xE03a95A5f1681c80D9308A4E571cE9Ee8977F3260xf4dFCf0EF472E8aaD3783479051f61EC574C6A8E
CawActions_L2bArbitrum0xb1589314B79BBE6e9c47d9641149795Db2adb9390x31e8F103F717C48c5FA6c9b9134a2AD1aEe8b1aE
CawCapOracle_L2bArbitrum0x595a4413797Eba8dCA76F37A8f6635B22Bf378E50x206c99Ee5CFF8b5D761926ff224D867E1fBC7aaa
CawChallengeRelay_L2bArbitrum0x09Ee733Eb6BA19dEBC0E576AA18333A9A5A6D5460x9ac02C514A016c7E6A92cf69a44a4d793b6b9cfE
CawProfileLedger_L2bArbitrum0x29225D1177d0ECB3C0309417197D493b827A75b00xd14C3038141C849612825760D9832515323462B5
PathwayExpander_L2bArbitrum0xc41aFf35C236f24404283ee909A2d0641E44fa420xdAD5bac641ABe10A11188A1AED7fAd282188A76a
SessionMessageParser_L2bArbitrum0x4faccdee61E46cEd81d8de719d77CB73a4e988930x5B930570017459E8d57e13b5B5052dd7Ed7C7B5f