MicroTrust Protocol

Technical overview

MicroTrust describes two credential roles on Base, Ethereum layer 2: a Master Passport for a human or organization, and a Child Passport associated with an agent. This overview identifies the published contract references and the current beta boundary.

Published contract references

Network: Base mainnet. Chain ID: 8453. Inspect the full addresses, code, and transaction history in the explorer before relying on a contract.

Master Passport
0x9885a8245333DfdefC7Eb40aa7c921C05228765B

Child Passport
0x51C9A031dCcCa9fAC40D30F98355DBBE635143AB

These are the addresses published by this project. A contract address or deployed bytecode is not evidence of an independent security audit or a guarantee that a particular permission is enforced.

How the model fits together

A principal is represented by a Master Passport.
An agent can be associated with a Child Passport.
A consuming application checks the relevant identity and authority before allowing an action.
The application and settlement system must enforce the permissions and limits that apply to that action.

Beta application process

Submit a beta application with your name and email. An optional social handle, referral source, or avatar may help identify your application. The form stores an application for review; it does not initiate an on-chain transaction. Keep the on-screen receipt and contact Marc for a status update.

Before integrating

Request the current ABI, supported contract version, ownership and upgrade controls, revocation behavior, and a test environment from Marc. A stable SDK and complete production integration specification are not published here yet. Treat protocol diagrams and roadmap statements as design context until the particular behavior has been verified.

Keep secrets out of applications

Never submit a seed phrase, private key, password, identity document, or financial account details through the beta form. Public blockchain records cannot generally be removed by the site operator.