IIBUKI GARDEN

Documents · Field record 00

Before trust,inspect.

This page is a living record of the current Base Sepolia rehearsal and the gates that must close before Base Mainnet.

Network
Base Sepolia · 84532
Generation
v6 · salt v6
Deployed
16 August 2026
Source verification
Not run on testnet

Rehearsal status, not a Mainnet assurance

The v6 contracts passed the Base Sepolia end-to-end ceremony (plant ×10, finalize, care, next-grove creation), but their source code has intentionally not been verified on the explorer. “Publicly verifiable” becomes true only after the source and proxy-link checks below are complete.

Architecture

One Grove,two living contracts.

The Factory uses EIP-1167 minimal clones. Each Grove receives its own Anchor and NFT address while sharing audited implementation bytecode.

  1. 01

    Factory

    Creates deterministic Anchor and NFT addresses.

  2. 02

    Implementations

    Hold the shared Anchor and NFT source logic.

  3. 03

    Grove clones

    Keep each Grove’s state at its own addresses.

  4. 04

    Explorer links

    Prove which verified implementation each clone delegates to.

Current deployment

Base Sepolia · v6

Addresses are copied from the checked deployment record. Open any row in BaseScan to inspect its bytecode and transactions.

Factory0xA625F2C1dbF213B7773FBcce174898b377d87bb0Creates and indexes every GroveSeries Registry0x3Bc381F988e5E912467BD2ad6DE8a22B9dFe2E86Write-once series registrationAnchor implementation0xdA70B1747c97073ce639949cB516718326543F76Shared Grove state logicNFT implementation0xd54553cA9f92af7D61C368C5e78777F637d136b9Shared ERC-721 and metadata logicGrove 0 Anchor0x2C0c8d6E144dE9A53728089a651383076D3975C3Finalized Grove clone (10 trees, Groundkeeper)Grove 0 NFT0x95c96C0FCb116e213bd8F1597a2D68fc1B71C5adGrove 0 NFT cloneGrove 1 Anchor0x85865319BC0f4018e91b6B87E39C6095A0550ce5Active Grove cloneGrove 1 NFT0x56aA23418C481d47446BE15a4028bb3466b627fcGrove 1 NFT cloneChunks Renderer0xEF89A207616B6E3D7C309b13C57f1fda9B457d2920 onchain application chunksModel Renderer0x87B3d8476A875C2e36746709A6235Db239d8d86927 onchain model chunksMetadata Renderer0x4d03F0ddB762c1438B7d18E93FbD01A0779458dcSVG and HTML metadataHSL Color Library0x79671f6a1fB557b9Dbc633ef744A30264371f9C4Shared color calculation libraryIshibumi0xAfDf2fc900F24137F6Ee68F255a2a623f8F2b835Inscription and signed-letter recordCornerstone0x5c56d8a6cEbA212c1f96ABfcd3477c0d1566Ac1bStores canonical document fingerprintsDocument Lineage0xF3433Ae7A2D3DFc7180867A5b56f25C5E7c00B44Append-only reasons for document changesProof of Gift0x32A04d791dCF4Ac7f1D79b2c466fe10041b48Ff8Signed memory recordBlocked Slots Storage0x8b527CFA9Cc9a25Ac2b677dDbd7d5DE6C8b2Bd22Onchain blocked-slot bitmap

Responsibility and lineage

Lineage — when something changes, the reason is recorded.

Portable documents carry previous-sha256 and change-reason. The record stays readable outside the chain.

IbukiDocumentLineage is append-only, has no owner, and rejects an empty reason. This is how 「かわるときは わけをいう」 is enforced.

Canonical document IDs

  • ibuki.record-format
  • ibuki.constitution
  • ibuki.cornerstone-text
  • ibuki.regeneration-guide
  • ibuki.records
Open Document Lineage on BaseScandocument/IBUKI_RESPONSIBILITY.md

Verification mechanism

What exists today.

The direction is correct, but the current automation is not yet strong enough to make “every Grove is verified” a Mainnet promise.

Already implemented

After cron creates a new Grove and confirms its event, the Worker can submit both the Anchor and NFT addresses to Etherscan V2’s proxy-verification endpoint. It runs only when the explorer API secret is configured.

Still missing for Mainnet

  • • The verification chain is currently fixed to Base Sepolia (84532), not Base Mainnet (8453).
  • • Grove 0, created during the initial deployment, is outside the cron verification path.
  • • The expected implementation address is not supplied to the proxy-verification request.
  • • Submission failures are non-fatal and there is no confirmation poll, durable status, or automatic retry queue.
  • • The initial implementation and standalone contracts still need a complete deployment-time verification ceremony.

Mainnet gate

Owner sign-off,to the last Grove.

Explorer verification is not an onlyOwner transaction and does not require spending gas. The Owner’s important role is to review the evidence, resolve failures, and sign the operational record before the ceremony closes.

  1. 01Verify every implementation and standalone contract from the exact deployment build.
  2. 02Verify the Factory, including constructor arguments for both implementation addresses.
  3. 03Register Grove 0 and every later Anchor/NFT clone as a proxy to its expected implementation.
  4. 04Poll the explorer until verification is confirmed; a submission GUID alone is not a pass.
  5. 05Store each result durably and expose it in the public Grove record.
  6. 06Require a human Owner sign-off before calling the deployment ceremony complete.

Verification is a record,not a badge.

The goal is not merely to show a green check. It is to let any visitor trace a Grove back to the exact code that governs it.

Return to the garden