arkiv-graph
Explore your app's Arkiv entities in tables and a graph, with wallet-signed Lifetime Extension and deletion.
Tiramisu testnet (7738577).
npm install arkiv-graph@0.3.1Setup, limitations and agent prompt
Prompt for your agent
Integrate arkiv-graph@0.3.1 into my app using its public npm API. First read https://github.com/SantiagoDevRel/arkiv-graph/blob/v0.3.1-docs.1/packages/arkiv-graph/AGENTS.md and the linked README; do not assume node_modules instructions load automatically. Ask me for the target network, public owner address, app namespace/type attributes and relationship rules. Start with a read-only table and graph from the same scoped query. Use the published package; do not copy its implementation. For wallet mutations, also read https://github.com/SantiagoDevRel/arkiv-graph/blob/v0.3.1-docs.1/apps/example/AGENTS.md. If I request Lifetime Extension or deletion, follow that integration, verify account/network/owner, obtain explicit deletion confirmation and confirm the transaction before reporting success. Never request a private key in chat or frontend code. Test the installed package, empty/error states and rendered layouts, and report exact versions and any unverified steps.
- Sample setup
- Node.js 22 and pnpm 9. Clone tag v0.3.1-docs.1, run pnpm install --frozen-lockfile, then pnpm dev. Open localhost:3012. The sample consumes the exact published npm version. No env file is required for reads.
- Prerequisites
- Explore the public social example without a wallet. For your app, supply its public owner and namespace attributes. Creation, Lifetime Extension and deletion require an injected wallet such as MetaMask or Rabby and test GLM from the Hub faucet. No private keys in the app.
- Supported network
- Tiramisu testnet (7738577).
- Arkiv SDK
- @arkiv-network/sdk 0.8.0; viem 2.56.3. SDK 0.6/0.7 clients are not supported by this release.
- Limitations
- Public data; filters do not provide privacy. Relationships are resolved by the library, not SQL joins. The sample loads up to 500 entities and marks partial results. Refresh is manual or follows a confirmed mutation. Expiration dates are estimates. Deletion has no undo or cascade and does not erase chain history. The hosted query endpoint allows 60 requests per IP per minute.
- Last verified
- 2026-09-09