Identity persists.
Authority stays scoped.

Stage record

Modes: Local 2 · Sponsor live (non-spending) 12 · Confidential (CRE) · deployed 4 · Testnet live (spends HBAR) 6. Stages 11 and 60 show their successful re-run; stage 50 ran twice and shows its second run (the Agent funding).

Key public references

Workflow facts

Name

identity-confidential-production (CRE project workflows/, target production-settings)

Handler

cre.handlerInTee(httpTrigger, onHttpTrigger, [{ tee: 'nitro', regions: ['us-west-2'] }]), routing five operations: admission, investor eligibility, credential, offering and distribution

Registry / DON family

private (Chainlink-hosted) / zone-a

Owner

0x7075057f1589BAf347cB6dD6a993B1FC536B8a0a

Deploy #1 · 17:38 UTC

ID 00e12517fc06c8984befaa63accbadb21b8c4abe529595fcf48542ba097ad250
binary 9902db587a3878b07ad03d599cb9c781f7c77b8ea440b168d8c42fd18b3fb9fb
config 7cb69b7b82f6d8a0701ba39b15cc915d6ea3b4ca746c84fd3a805188c38098f8 — pins the Bootstrap Configuration hash; no issuer rules yet

Deploy #2 · 19:36 UTC

ID 0000e58d50da8eaf29fb4212c236f374d11d7eb2452502c3bad0afe74d3f25c8
same binary 9902db58…, new config e7703b193460430b4767b89d44caea2620eda5b3c844deee69f9db9436207d1d adding credentialRules. The CLI updated the workflow in place

Pinned in deploy #2

credential type CatenorInvestorEligibilityCredential; the only accepted issuer did:catenor:656d66dff9ce1db692786ee241bc3cab#assertion-key-1, public key z6MknrBa8Vbrsz5YCoBhgmV54ALJP9p1YSocpeBvgzBgJVXq; status at most 600 s old; policy:offering-eligibility:v1 and policy:distribution-eligibility:v2

Vault DON secrets

CATENOR_INTERNAL_API_TOKEN · SUMSUB_APP_TOKEN · SUMSUB_SECRET_KEY (namespace main; names only, no value was printed)

Trigger

HTTP trigger with one authorized EVM key 0x18487BeFE194528cf429f5889BAE3aCbdA104a6c, called as JSON-RPC workflows.execute with an alg: ETH JWT

Gateway

https://01.gateway.zone-a.cre.chain.link

Result path

callback to the Railway relay https://catenor-one-production.up.railway.app/v1/internal/cre/identity-confidential/results; the local runner pulls each HMAC-authenticated result, re-authenticates it and delivers it

Uploaded configs

public data only: the callback URL, the hashes, the evidence-acceptance rules, the issuer key and the trigger address

The five executions

Execution IDs come from two places: the gateway’s workflow_execution_id and the platform’s cre execution list. From stage 42 on they ran on deploy #2.

Findings for Chainlink, reported as observed

1. The gateway URL. The docs’ private-registry gateway https://01.enterprise-gateway.zone-a.cre.chain.link/ answered -32600 Workflow not found for two ACTIVE private-registry workflows — the confidential one and a minimal non-TEE control workflow, catenor-http-control (0038de78…a66f). https://01.gateway.zone-a.cre.chain.link, the only gateway URL embedded in CRE CLI v1.33.0, accepted the same signed request at once (HTTP 200, ACCEPTED).
2. User logs are visible. The simulator banner says user logs “will not be visible, and will not leave the TEE”. On the deployed platform the Logs tab shows them from several DON nodes (Node 1, 2, 4, 5, 8, 9…). The workflow logs only non-sensitive markers through safe-log.
3. Several callbacks per execution. Each node’s copy calls back. The relay keeps the first authenticated result per run and answers 409 LATE_OR_DUPLICATE_RESULT to the rest.
4. Secrets. cre secrets create parses CRE_ETH_PRIVATE_KEY from the .env it is given, even with --secrets-auth browser; the template’s non-hex placeholder fails with invalid hex character 'Y'.
5. Enrollment. The first Confidential Workflow deploy on this account needed no extra enrollment step.

Screenshots

Wallets and Privy policies

Read back live in stage 92 and checked against the dashboard. Everything not listed is denied; exports are denied everywhere.

The Agent’s Privy policy, rule by rule

Stage 92 read-back: “Agent policy exactly the approved boundary: true.”

The SPV’s Privy policy after the equity existed

The factory rule came first. After deployEquity, the SPV management-owner key (outside the runtime) added three Privy policy rules, each pinned to the new equity. Six rules in all.

Stage 92 read-back, as stored by Privy

{
  "id": "p99xe36icsfvewrovm1mczwq",
  "version": "1.0",
  "name": "catenor-one-distribution-agent-3d8dc074",
  "chain_type": "ethereum",
  "rules": [
    {
      "id": "fxxhjsvbzc7dl9xx9lhybkqz",
      "name": "allow-distribution-payout-hedera",
      "method": "eth_signTransaction",
      "action": "ALLOW",
      "conditions": [
        { "field_source": "ethereum_transaction", "field": "chain_id", "operator": "eq", "value": "296" },
        {
          "field_source": "ethereum_transaction",
          "field": "to",
          "operator": "in",
          "value": ["0x7de572532820B22040B561e68543419419b72473", "0xCfCa833A8e6b7651E44480b92822576BcB78Da73"]
        },
        { "field_source": "ethereum_transaction", "field": "value", "operator": "lte", "value": "0x1158e460913d00000" }
      ]
    },
    { "id": "su9uq4lrxg8hgsusvgm3nv3q", "name": "deny-exportPrivateKey", "method": "exportPrivateKey", "action": "DENY", "conditions": [] },
    { "id": "nu05o2k3j0kinl728wimu2c9", "name": "deny-exportSeedPhrase", "method": "exportSeedPhrase", "action": "DENY", "conditions": [] }
  ],
  "_note": "Transcribed from the Privy dashboard (policy JSON tab) on 2026-09-12 after stage 70, final-demo instance c1-202609121659. 0x1158e460913d00000 = 20 HBAR (18-decimal weibar). The two addresses are the investors' receiving wallets. Public data only."
}

{
  "id": "cygll4bmgocqr05asp2w6f2s",
  "version": "1.0",
  "name": "catenor-one-spv-execution-4c875d44",
  "chain_type": "ethereum",
  "rules": [
    {
      "id": "t01al94fattl6okgua0jwpd0",
      "name": "allow-ats-factory-hedera-testnet",
      "method": "eth_signTransaction",
      "action": "ALLOW",
      "conditions": [
        { "field_source": "ethereum_transaction", "field": "chain_id", "operator": "eq", "value": "296" },
        { "field_source": "ethereum_transaction", "field": "to", "operator": "eq", "value": "0xd1F118A40f3b02883D35909eF2517e7EDd78379d" }
      ]
    },
    { "id": "nfob7nm7jo55mjuj3bbxq6ii", "name": "deny-exportPrivateKey", "method": "exportPrivateKey", "action": "DENY", "conditions": [] },
    { "id": "ub7kylldhvex9z8iq08imioj", "name": "deny-exportSeedPhrase", "method": "exportSeedPhrase", "action": "DENY", "conditions": [] },
    {
      "id": "r6bo3tyjsl1glf3vwimo3m0g",
      "name": "allow-setDividend-equity",
      "method": "eth_signTransaction",
      "action": "ALLOW",
      "conditions": [
        { "field_source": "ethereum_transaction", "field": "chain_id", "operator": "eq", "value": "296" },
        { "field_source": "ethereum_transaction", "field": "to", "operator": "eq", "value": "0xf37A91c3aC757ac5f14e4b8BC92D4b1001D97ABC" },
        { "field_source": "ethereum_calldata", "field": "function_name", "operator": "eq", "value": "setDividend", "abi": "[setDividend((uint256 recordDate,uint256 executionDate,uint256 amount,uint8 amountDecimals) newDividend) returns (uint256 dividendId_)]" }
      ]
    },
    {
      "id": "snvx2odgylm68pz4x14hn3uc",
      "name": "allow-issueByPartition-equity",
      "method": "eth_signTransaction",
      "action": "ALLOW",
      "conditions": [
        { "field_source": "ethereum_transaction", "field": "chain_id", "operator": "eq", "value": "296" },
        { "field_source": "ethereum_transaction", "field": "to", "operator": "eq", "value": "0xf37A91c3aC757ac5f14e4b8BC92D4b1001D97ABC" },
        { "field_source": "ethereum_calldata", "field": "function_name", "operator": "eq", "value": "issueByPartition", "abi": "[issueByPartition((bytes32 partition,address tokenHolder,uint256 value,bytes data) _issueData)]" },
        { "field_source": "ethereum_calldata", "field": "issueByPartition._issueData.partition", "operator": "eq", "value": "0x0000000000000000000000000000000000000000000000000000000000000001", "abi": "(same issueByPartition ABI)" }
      ]
    },
    {
      "id": "myjpkp43eogob04pvjjmg20x",
      "name": "allow-grantRole-corporate-action-to-spv",
      "method": "eth_signTransaction",
      "action": "ALLOW",
      "conditions": [
        { "field_source": "ethereum_transaction", "field": "chain_id", "operator": "eq", "value": "296" },
        { "field_source": "ethereum_transaction", "field": "to", "operator": "eq", "value": "0xf37A91c3aC757ac5f14e4b8BC92D4b1001D97ABC" },
        { "field_source": "ethereum_calldata", "field": "function_name", "operator": "eq", "value": "grantRole", "abi": "[grantRole(bytes32 _role,address _account) returns (bool success_)]" },
        { "field_source": "ethereum_calldata", "field": "grantRole._role", "operator": "eq", "value": "0xa1acfc499025c99f55059195e6276f639d34a18aad7b8121b9192b7f438c55cd", "abi": "(same grantRole ABI)" },
        { "field_source": "ethereum_calldata", "field": "grantRole._account", "operator": "eq", "value": "0x182F8c7DDbDa1b5f295893E2c4f6D55abBdB9926", "abi": "(same grantRole ABI)" }
      ]
    }
  ],
  "_note": "Copied by the maintainer from the Privy dashboard (policy JSON tab) on 2026-09-12 after stage 60, final-demo instance c1-202609121659. The full ABI arrays of the calldata conditions are abbreviated here to their signatures; everything else is verbatim. Public data only."
}

Screenshots

Accounts

The asset lifecycle, each step gated by Catenor

Final state · stage 91, 22:54 UTC

Bootstrap funding

Testnet gas and account activation, not a distribution. The Privy treasury received 100 ℏ from the portal faucet, then sent:

Prize fit: “Tokenization of Anything”

• Asset Tokenization Studio v8 contracts through the official Factory. Issuance: issueByPartition ×2. Configuration: the corporate-action role and the dividend. Lifecycle: the dividend entitlement plus the distribution.
• Deployed and demonstrated on Hedera testnet, verifiable on HashScan.
• An ineligible holder is visibly blocked: entitled to 4, received 0.

Screenshots

Audit events by type

The counts include the three abandoned stage 11 attempts (ADMISSION_REQUESTED 4, CONFIDENTIAL_VERIFICATION_REQUESTED 4, CONFIDENTIAL_EVIDENCE_VERIFIED 1). INVESTMENT_EXECUTED is 2 of 4 INVESTMENT_AUTHORIZED: the dry runs authorize without executing.

The authority chain

Relationships, capabilities and delegation are public-key-verifiable authority with no sensitive input, so none of this runs in the CRE, by design.

The Agent’s grant runs 20 days, inside the Sponsor’s 30: delegated authority stays within the delegator’s authority.

Every refusal in the run

Three of them are DISTRIBUTION_REQUEST_DENIED audit events. The rest are refusals at the authority, presentation or signer boundary.

Verify it yourself

From the repository root. All read-only.

1. scripts/demo/90-show-cre-execution.sh — the CRE executions: the local sanitized records against the CRE platform’s own execution list.
2. scripts/demo/91-verify-hedera.sh — public chain data, no keys: the JSON-RPC relay and the Mirror Node. Anyone can run it.
3. scripts/demo/92-verify-privy.sh — Privy wallets().get / policies().get read-back. Needs the Privy app credentials.
4. scripts/demo/93-verify-catenor-audit.sh — re-verifies the audit hash chain, the Trust Anchor, the authority chains and the credentials from the recorded signed documents (the run records stay local and git-ignored).
5. scripts/demo/99-verify-complete-demo.sh — every stage record plus the Catenor verification, in one summary.

Screenshots

The day, in phases (UTC)

Incidents

1. Stage 11, attempts 1–3: the documented gateway does not serve this organization. Attempt 1 got CRE gateway HTTP 400 with no detail; the verifier now surfaces the gateway’s code and message. Attempt 2 got -32600 Workflow not found, although cre workflow list showed the workflow ACTIVE. A minimal non-confidential control workflow (catenor-http-control, 0038de78…a66f) isolated the cause: the same signed request failed on the documented enterprise gateway and was ACCEPTED on https://01.gateway.zone-a.cre.chain.link. The verifier’s default gateway changed (overridable with DEMO_CRE_GATEWAY_URL). Attempt 3 ran while the fix was still being written. Attempt 4 was admitted. No attempt created an execution or consumed the set-once root.
2. secrets.sh failed on the CRE_ETH_PRIVATE_KEY placeholder. The CLI parses that key from the .env it is given, even in browser mode: invalid hex character 'Y'. Fixed with a fresh random, unfunded key, written without printing it. It is not linked to the account and is not the trigger key.
3. Stage 60 recorded the asset reference instead of the address, after a successful deployEquity, and failed with invalid equity or SPV address. The runner now records the checksummed address and the reference separately, and never redeploys an existing equity. The 21:25 UTC re-run reported “already deployed … no new deployment” and completed the owner-authorized SPV Privy policy extension. The equity was not deployed twice.
4. A transient CLI account error after deploy #2 (“unable to retrieve organization info… try again in a few minutes”). A re-run a few minutes later was clean; deployed triggers do not depend on the CLI session.
5. An unneeded 25 HBAR SPV top-up in the second funding run: the script tops up any wallet below its suggested amount. Accepted to save time; it is testnet HBAR and the SPV had no further transactions.
6. An earlier instance was stopped. c1-202609121438 was stopped after stage 11 because its admission ran on CRE simulation. The final run restarted on a new Privy app so that the admission also ran on the deployed workflow.

The gateway control experiment

Honest labels