It never sleeps
Cron keeps the agent working through the night. A single bad instruction repeats on every tick until a human happens to look.
Your agent. Your rules.
Autonomous agents run unattended and sign their own transactions. Kavonyx is the earthwork between the agent and its wallet on BNB Smart Chain — four ramparts a transaction must cross before it reaches the chain. Drawn once. Held by you.
Kavonyx
Owner-controlled transaction limits for autonomous agents on BNB Smart Chain. The owner draws the sheet. The agent works inside it.
The siege
Cron keeps the agent working through the night. A single bad instruction repeats on every tick until a human happens to look.
Hand over a private key and the agent can do anything the key can — drain, grant infinite approval, bridge the balance out.
Signing every move by hand turns autonomy back into a chat window. The answer is standing walls, not a sentry you have to wake.
Four ramparts
Per-transaction, per-hour and per-day ceilings. A runaway loop fills the ditch and goes no further.
Only named contracts and functions pass. Unknown targets and infinite approvals are turned back.
Large moves wait in the gatehouse. You have a window to drop the portcullis.
One owner-only command seals the works. The agent cannot open it from inside.
The sheets
General plan / The works
Sheet II
Each rampart answers one question about a transaction. A transaction lands only if every answer is yes. They are checked in order, outermost first, and the first refusal ends the approach.
The outermost line. Every transfer of value is counted against ceilings per transaction, per hour and per day. When a ceiling is reached the ditch is full: nothing more crosses until the window rolls over. This is what stops a loop that repeats a bad instruction on every cron tick.
A continuous wall with one gate. The agent may call only the contracts you named, and only the functions you named on them. Everything else meets the wall. Unlimited token approvals are refused outright, because an infinite approval is a hole in the curtain that outlives the transaction.
Moves above a threshold are not refused — they are held in the gatehouse for a fixed delay. During that window the owner can drop the portcullis and cancel. If nobody does, it can be released once the delay has passed. Autonomy is kept; surprise is removed.
The last place to retreat to. One owner-only command freezes every outgoing transaction at once — including anything waiting at the gate. The agent sits inside the walls and has no key to the keep; it cannot lift the freeze, and it cannot remove the owner.
Rulings
| Approach | Ditch | Curtain | Gate | Keep | Ruling |
|---|---|---|---|---|---|
| buy 0.04 BNB on listed router | under cap | listed | below threshold | open | PASSED |
| approve(MAX) to unknown address | — | refused | — | — | TURNED BACK |
| same buy, 40th time this hour | cap reached | — | — | — | TURNED BACK |
| send 0.80 BNB to treasury | under cap | listed | over 0.50 | open | HELD 6h |
| any move after owner freeze | — | — | — | sealed | TURNED BACK |
General plan / The drawing
Sheet III
Every limit lives on a single order of works. The owner draws it; the agent works inside it. Each revision is numbered on-chain, so the sheet in force can always be traced.
Example sheet
The sheet uses the same four words as the fort. If you can read the plan, you can read the policy. Values below are an example for a trading agent, not defaults.
; order-of-works — kavonyx.policy
; rev 3 · owner-only
agent growth-01
ditch perTx 0.10 BNB perDay 1.00 BNB
curtain allow Router[buy,sell]
allow Token[transfer]
; approve(MAX) always refused
gate hold > 0.50 BNB delay 6h
keep owner 0xYourWallet… freeze owner-only
Fields
| Field | Rampart | Meaning |
|---|---|---|
agent | — | The signer this sheet governs. One sheet per agent. |
ditch.perTx | Ditch | Largest value a single transaction may move. |
ditch.perHour / perDay | Ditch | Ceilings per clock hour and UTC day. Reaching one fills the ditch until the next window opens. |
curtain.allow | Curtain | Contract address plus the function selectors permitted on it. |
approve(MAX) | Curtain | Unlimited approvals are refused by the contract itself, whatever the allow list says. |
gate.hold | Gate | Threshold above which a move is queued instead of sent. |
gate.delay | Gate | How long a held move waits before the agent or owner may release it. |
keep.owner | Keep | The only address that may revise the sheet, cancel, or freeze. |
Order of ruling
Is the fort sealed? If frozen, turned back immediately.
Is the target and function on the sheet? Unlimited approvals never pass.
Does the value fit under every ceiling?
Is it over the hold threshold? If so, queue with a release time.
Sent, and logged on-chain. A refusal reverts with the rampart that stopped it.
The keep is checked first, even though it is the innermost work: a sealed fort turns everything back without spending effort on the other ramparts.
General plan / Construction
Sheet IV
A fort that is only on paper protects nothing. This sheet says plainly which works stand and which do not yet.
Order of construction
Policy sheet format, the ruling model, the order of ruling, and these sheets.
All four ramparts written and passing 36 tests, including fuzzing on the day cap and unlisted targets and reentrancy through every entry point. CI runs them on every push. Not yet audited. Not deployed on BNB Smart Chain. No reference vault is published, and no real funds should be sent to anything claiming to be one.
TypeScript on viem, aimed at BNB Smart Chain. Every move is simulated first, so a refusal comes back with the rampart that stopped it before any gas is spent. Passing end-to-end tests against a local chain. Native gas is BNB; on testnet it is tBNB.
Reads a vault from BNB Smart Chain; owners can seal the keep and drop the gate from their own wallet. Open the table.
Questions
The vault contract is written and tested. It is not deployed on BNB Smart Chain, and it is not audited. There is no reference vault to open. Do not send real funds to anything claiming to be a Kavonyx vault.
No. KVNX is the proposed token symbol for Kavonyx. There is no published contract, supply, or liquidity. Do not send funds to an address that claims to be KVNX.
The design is that funds sit in a vault you own; Kavonyx rules on what may leave it. The owner key never goes to the agent and never goes to us.
No. Kavonyx does not try to guess whether a contract is good or bad. It enforces limits you set, whatever the agent is told to do. A scanner can be fooled by a new trick; a cap cannot.
Only at the gate, and only for moves you decided are large enough to wait. Everything under the threshold lands without delay and without a prompt.
No. Figure 1 on the general plan is an illustration of how rulings work. It is labelled as such.
General plan / The name
Sheet V
Kavonyx is the name of this vault framework. The owner sets the rules; the agent works inside them, on BNB Smart Chain. The mark is four guards around an open centre. It is not a letter.
Your agent. Your rules. The owner draws the sheet. The chain reads it. The agent does not redraw it.Kavonyx
The method, our ramparts
Bastions were angled so that every metre of wall could be covered by fire from another. No approach went unwatched.
In KavonyxEvery transaction is ruled on. There is no path to the wallet that skips the ramparts.
Ditch, covered way, ravelin, curtain, then the keep. Losing one line did not lose the fort.
In KavonyxFour independent ramparts. A bad prompt that slips past the allowlist still meets the cap and the gate.
The forts that lasted were designed against the way a place is actually taken.
In KavonyxDesigned against how agents actually fail: loops, injected instructions, infinite approvals, leaked keys.
The story
Kavonyx is the vault an owner draws around an autonomous agent on BNB Smart Chain. The owner sets the rules once. The agent works inside them and cannot redraw the sheet. Figure 1 shows that approach. It is an illustration. KVNX is a proposed symbol. It is not a deployed token.
Works unattended and signs its own transactions. A raw key can drain, approve without limit, or send the balance out.
Draws one sheet. Only the owner can revise it, cancel a held move, or seal the keep.
Counts every transfer against ceilings per transaction, per hour, and per day.
Lets through only named contracts and functions. Unlimited approvals are refused.
Holds a large move until the delay passes. The owner can drop it before then.
One owner command freezes every outgoing move. The agent cannot lift it.
General plan / Owner's table
Sheet VI
Paste a vault address to read its state from BNB Smart Chain. Native gas is BNB; on testnet the same vault would use tBNB. If your wallet is the owner, you can freeze the keep and drop the gate on held moves. Nothing here can move funds out.
—
—
—
—
delay —
—
—