Documentation

Build a Resilient On-Chain Identity

The future of Web3 belongs to high-intent, active users. Our platform provides the necessary infrastructure to enhance your wallet's on-chain footprint through verified, organic interactions.

• Protocol-Ready Profiles: Transform your address into a highly active participant, recognizable by any ecosystem.
• Deep Transaction Density: Build a robust, verifiable transaction history that aligns with organic user behavior and naturally stands out to anti-Sybil algorithms.
• Long-Term Engagement: Maintain consistent, measurable activity to stay visible and eligible for future opportunities.

Stop being a ghost address. Start building your on-chain legacy today.

AutoActivity: Tools for Automated Actions

We provide tools to automate repeatable actions (daily GMs, contract deployments, NFT mints) to be consistent and never miss a day of activity. They are implemented via a relayer: you sign an authorization once, and our service submits the daily transactions on your behalf. Using a relayer is a standard practice in Web3.

The same pattern appears everywhere: meta-transactions, gasless transactions, account abstraction. Examples include NFT lazy minting, sponsored transactions, gasless approvals. In all these cases the transaction sender is not the same as the user whose activity is recorded.

The AutoActivity is on-chain, transparent, auditable, indexed by block explorers and analytics tools, and tied to your address. Nothing is hidden or spoofed — this is not "fake" or "spam" activity.

Send a "GM" transaction on-chain once per day to demonstrate consistent protocol interaction. The contract tracks your streak (consecutive days) and total GM count.

Every day, deploy a lightweight smart contract and become its rightful owner. When you deploy it, the contract automatically records you as the sole owner and adds a fresh on-chain timestamp. This builds your developer activity footprint, growing your contract total count and increasing your deployment streak.

You own every contract forever. Each one comes with a built-in interaction method, simply share the address and let anyone ping it.

It means, your contracts aren't isolated. Once deployed, they can be used by anyone. Every external interaction becomes a signal that your contract is not just deployed — it's being used. Over time, this makes your address look like a source of on-chain utility, not just activity. You become a builder contributing to the chain, not just a user.

Mint lightweight ERC721 tokens to add authentic on-chain activity: one mint = one transaction from your wallet. Each collection is a separate contract; you pay the mint price (if any) and network gas.

Mint NFTs — full doc →

Go beyond GMs and deploys — use real on-chain projects to diversify your wallet's activity. The Explore page curates projects that generate verifiable transactions from your address.

Explore — full doc →

Streaks are calculated on-chain using block.timestamp / 86400 (UTC day boundaries).

• Streak increments if you interacted on the previous day (day - 1)
• Streak resets to 1 if you miss a day
• View functions return 0 if the streak is already broken

AutoGM and AutoDeploy use EIP-712 typed data signatures for authorization:

• Domain includes chain ID and contract address (replay-safe across chains)
• Signed message securely encapsulates the user address, nonce, and deadline
• Same signature is reused daily by the relayer until expiry
• Use the "Cancel subscription" button on the platform to both revoke on-chain and remove your subscription from our relayer database — otherwise the relayer would keep retrying until the deadline. Or, call incrementNonce() to revoke your authorization at any time. This invalidates your signature on-chain.

Two timestamps govern AutoGM and AutoDeploy:

• deadline — part of the EIP-712 signed message. Limits how long the relayer may use your signature. The contract rejects any relay after this time.
• autoGMUntil / autoDeployUntil — on-chain value. The timestamp until which your subscription is paid. The contract rejects relays if this has passed.

When you subscribe through the platform, deadline is set to the end of the last paid day (same logic as the contract). Both checks align: the relayer uses the deadline stored in our database and does not need extra RPC calls to verify subscription status.

Important: If you extend your subscription by calling purchaseAutoGM() or purchaseAutoDeploy() directly (e.g. via Etherscan) without re-registering through the platform, the on-chain subscription will extend, but your signature's deadline will not. The relayer cannot use an expired signature. To keep AutoGM/AutoDeploy working after extending, re-subscribe through the UI so you sign a new message with an updated deadline and give us updated permission.

Our core contracts are deployed across multiple supported networks. Each blockchain maintains its own independent state and user history. We are continuously working on expanding the range of supported networks to provide broader accessibility.