Does the device own itself?
Does the device own itself?
No. The agent NFT is owned by the wallet that claimed it. The device holds a separate key that can spend inside the vault limits and sign attestations. It is never an operator on the NFT.
I changed chain.owner in the config. Did the owner change?
I changed chain.owner in the config. Did the owner change?
No.
chain.owner is only used to build the claim link. After claim, the owner is ownerOf on the Identity Registry. Transfer the NFT to move it.I edited per_tx_cap in the config and the vault did not change.
I edited per_tx_cap in the config and the vault did not change.
Those config values are the caps sent at claim. Later changes go through
/limits or a direct tightenCaps / loosenCaps call. The vault is the source of truth.Why does attest revert with NotOperator?
Why does attest revert with NotOperator?
The owner has not approved KineticAttestor on the agent NFT. The claim page sends
setApprovalForAll after claim. If that transaction was rejected, send it from the owner wallet. The attestor address is on Deployments.The device says the spending cap is too low to top up gas.
The device says the spending cap is too low to top up gas.
The vault has MON, but one top-up cannot lift the device address above 1 MON without breaking a cap. Send a little MON to the device address, or raise the caps. The thresholds are in Funding and gas.
Can I send MON straight to the vault address?
Can I send MON straight to the vault address?
No. The vault reverts a plain transfer, because the transfer does not say which agent to credit. Use
deposit(agentId) or the /deposit link.Someone messaged my bot. Can they spend?
Someone messaged my bot. Can they spend?
Owner commands and the paired chat are limited to the Telegram account that sent
/bind with the one-time code. Spending still needs the vault rules, and loosening a limit needs the owner wallet. Another chat gets the unpaired reply.Does an attestation mean the machine really did it?
Does an attestation mean the machine really did it?
It means the device key signed that record at that time, and the owner had approved the attestor. It does not mean the hardware moved. The full boundary is What an attestation proves.
Where do operation records go?
Where do operation records go?
After a successful
monad_attest, one canonical line is appended to ~/.kinetic/records/operations.jsonl, and the request hash to operation-requests.txt on the same line number. Nothing is stored when [records] has no fields.Can I list records from a chain other than testnet?
Can I list records from a chain other than testnet?
sell_data and the marketplace only accept chain id 10143 in this version. Mainnet has no KineticVM contracts yet, and the runtime refuses a mainnet config pointed at the testnet addresses.What happens to the vault if I sell the NFT?
What happens to the vault if I sell the NFT?
The balance stays with the agent. The old device stops working immediately, because
activeDevice reverts. Withdraw before you transfer if you want to keep the MON. The new owner releases the old binding and links their own device. See Ownership.Is this audited?
Is this audited?
No. The testnet deployment is unaudited. Read Trust and safety before you put anything you care about in a vault, and treat the MON as testnet MON.