Key Is Not Enough. Signature alone is not enough. Governed execution must still pass intent, policy, consequence, and evidence before it is treated as legitimate.
KINE Runtime
Connect a wallet once, then KINE can share that runtime context across Wallet Posture, Action Review, policies, and supporting evidence.
Hosted beta today
Read-only wallet context, Action Review, consequence explanation, structured records, and supporting evidence.
Governed execution path
A smart-account constitution can cap, delay, queue, pause, or veto routed actions inside the governed path.
Truth boundary
This website is read-only beta. Full enforcement requires the governed smart-account path and proof-backed activation.
Protection is not verified
No current wallet session exists, so KINE cannot verify an owner, chain, governed account, policy, Guardian, migrated assets, or activation evidence.
Current session
No connected wallet
Chain: not established
Activation progress
Complete each boundary before protection can be verified.
Connecting a wallet does not authorize deployment or move funds.
Review activation details
Eligibility, lifecycle, policy, Guardian, migration, and evidence context.
KINE can inspect and warn about an ordinary wallet today. Governed Protection adds a routed smart-account path where policy can enforce supported caps, delays, queues, pauses, and Guardian veto on the governed route only.
Current state
Governed protection is not active
Your connected wallet can still be inspected and warned about, and governed protection is available for supported Sepolia EVM paths.
Featured snapshot
A supported EVM wallet can begin governed activation on Sepolia.
Eligibility
Governed protection is available.
You can begin governed activation on Sepolia.
Protection now
Read-only protection only
Ordinary EOAs can be inspected, warned about, and tied to receipts and evidence, but KINE cannot veto a transfer directly from that wallet.
Governed adds
A verified governed account can enforce supported caps, delays, queues, pauses, and Guardian veto only on the routed execution path.
Fees / chain actions
Activation may require Sepolia on-chain deployment and policy-binding transactions. Network fees can apply. Connecting alone does not protect existing EOA assets.
Truth boundary
Truth boundary: Sepolia proof path only. Read-only inspection can warn and explain, but governed enforcement exists only inside a verified governed route.
Activation stage
Governed activation not started
Check eligibility
currentConfirm supported wallet and chain context.
Review protection
upcomingUnderstand what protection exists now and what governed protection adds.
Review policy
upcomingSee the limits, destinations, and Guardian boundary before consent.
Confirm setup
upcomingAcknowledge fees, chain actions, and custody implications.
Create governed account
upcomingPrepare the routed execution path on Sepolia.
Apply policy
upcomingBind the constitutional rules to the governed route.
Connect Guardian
upcomingBind Guardian to the governed activation path.
Verify activation
upcomingConfirm the governed state and evidence references.
Current EOA protection
Ordinary EOAs can be inspected, warned about, and tied to receipts and evidence, but KINE cannot veto a transfer directly from that wallet.
Governed protection
A verified governed account can enforce supported caps, delays, queues, pauses, and Guardian veto only on the routed execution path.
Policy review
The consumer surface shows only the truthful fields that the current proof path supports. Advanced details keep the full policy fingerprint available without making it the primary message.
Per-transaction limit
Not configured
not configured
Daily limit
Not configured
not configured
Allowed destinations
Not configured
not configured
Blocked destinations
Not configured
not configured
Delay threshold
Not configured
not configured
Queue threshold
Not configured
not configured
Guardian veto
Not configured
not configured
Recovery authority
Not configured
not configured
Policy version
Not configured
not configured
Policy hash
Not configured
not configured
Per-transaction limit
not configured
Daily limit
not configured
Allowed destinations
not configured
Blocked destinations
not configured
Delay threshold
not configured
Queue threshold
not configured
Guardian veto
not configured
Recovery authority
not configured
Policy version
not configured
Policy hash
not configured
Next action
Check eligibility to begin governed activation.
Asset migration is not performed in this gate. If a future governed route requires routed assets or selected actions, that will be explained before consent.
Eligible Sepolia EVM wallet
A supported EVM wallet can begin governed activation on Sepolia.
Eligibility: Governed protection is available.
Step: Check eligibility
CTA: Review Governed Protection
Proof: Evidence not yet prepared
Missing wallet context
Connect a supported wallet before governed activation can be checked.
Eligibility: Connect a supported wallet first.
Step: Check eligibility
CTA: Connect Wallet
Proof: Evidence not yet prepared
Unsupported Solana wallet
Solana stays in read-only protection for this governed path.
Eligibility: This wallet family stays in read-only protection for now.
Step: Check eligibility
CTA: Review Governed Protection
Proof: Evidence not yet prepared
Unsupported Bitcoin wallet
Bitcoin stays in read-only protection for this governed path.
Eligibility: This wallet family stays in read-only protection for now.
Step: Check eligibility
CTA: Review Governed Protection
Proof: Evidence not yet prepared
Review-required hardware context
Hardware wallets remain manual / public-address inspection until a supported routed path exists.
Eligibility: Review required before activation.
Step: Check eligibility
CTA: Review Governed Protection
Proof: Evidence not yet prepared
Deployment prepared
A governed account can be prepared, but not yet confirmed.
Eligibility: Governed protection is available.
Step: Create governed account
CTA: Prepare Protected Account
Proof: Evidence not yet prepared
Deployment submitted
The protected account deployment has been sent and is awaiting confirmation.
Eligibility: Governed protection is available.
Step: Create governed account
CTA: View Deployment Status
Proof: Evidence not yet prepared
Deployment confirmed
The governed account exists on Sepolia, but policy binding still needs confirmation.
Eligibility: Governed protection is available.
Step: Apply policy
CTA: Continue to Policy Setup
Proof: Evidence not yet prepared
Policy binding confirmed
Protection rules are confirmed and ready for Guardian binding.
Eligibility: Governed protection is available.
Step: Connect Guardian
CTA: Continue to Guardian Setup
Proof: Evidence not yet prepared
Guardian binding confirmed
Guardian is connected to the governed activation path, but activation is still proof-path only until verification is coherent.
Eligibility: Governed protection is available.
Step: Verify activation
CTA: Verify Activation
Proof: Evidence not yet prepared
Verified evidence package, not active
The evidence package can verify cleanly even before the account is active.
Eligibility: Governed protection is available.
Step: Verify activation
CTA: Verify Activation
Proof: Evidence verified
Active governed protection
Only this state can show the green active badge.
Eligibility: Governed protection is available.
Step: Governed protection active
CTA: View Governed Protection
Proof: Evidence verified
Degraded governed protection
A missing or mismatched governed component requires attention.
Eligibility: Governed protection is available.
Step: Governed protection needs attention
CTA: Review Protection Issue
Proof: Evidence not yet prepared
Recovery required
Recovery must complete before governed protection can continue.
Eligibility: Recovery is required before activation can continue.
Step: Recovery action required
CTA: Start Recovery Review
Proof: Evidence not yet prepared
Failed activation
The activation path could not be completed safely.
Eligibility: Ownership must be verified before activation.
Step: Activation could not be completed
CTA: Review Failure
Proof: Evidence not yet prepared
Ownership mismatch
Verify the wallet owner before attempting governed activation again.
Eligibility: Ownership must be verified before activation.
Step: Check eligibility
CTA: Review Governed Protection
Proof: Evidence not yet prepared
Proof path only
The governed route exists as proof path evidence, not active enforcement.
Eligibility: Governed protection is available.
Step: Verify activation
CTA: Verify Activation
Proof: Evidence verified
Awaiting consent
The setup is ready for a user to review and approve.
Eligibility: Governed protection is available.
Step: Confirm setup
CTA: Confirm Setup
Proof: Evidence not yet prepared
Review deployment preview
Construct and inspect source-bound deployment calldata without submitting a transaction.
KINE constructs deterministic KineSmartAccountV2 deployment calldata from the current Sepolia wallet identity and the constitutional values entered below. Previewing does not deploy, sign, broadcast, or mark the account protected.
Current session
No current wallet
Connect a wallet first
Chain: not established
Constitutional inputs
These values create a local immutable preview only. No provider transaction method is available in this component.
Connect a wallet to establish the current deployment owner.
KINE remains fail-closed. Complete the explicit inputs and construct the preview to inspect the exact source-bound transaction intent.
Advanced: live Sepolia deployment authorization
Real wallet authorization boundary. Open only after reviewing a valid deployment preview.
Live Sepolia authorization
This is a real contract-creation authorization boundary. Nothing executes automatically. A wallet request can occur only after every confirmation below is complete and you press the authorization button.
Connected owner
No connected wallet
Required network
Sepolia · Chain ID 11155111
Current chain: unknown
Final irreversible authorization
Enter the exact phrase below. This component can request one real Sepolia contract-creation transaction only after you press the button.
EXECUTE ON SEPOLIANo wallet authorization has been requested. No transaction has been submitted.
Demonstration status: Governed protection is not active
This fixture explains the lifecycle. It is not automatically treated as current-wallet protection evidence.
Research, proof, and implementation details
Sepolia proof history, evidence explanations, principles, scenarios, and implementation material.
Proof boundary
The 8BN2 receipt proves a controlled Sepolia KINE V2 scenario. It does not claim audited mainnet protection, real-fund safety, or universal protection for normal unguarded EOAs. This evidence only proves the tested smart-account constitution path: request, veto, apply attempt blocked, attacker remains untrusted.
Live Sepolia evidence snapshot
Request
Risky trust change was requested on KINE V2.
Veto
Guardian veto was stored on-chain.
Execution
Final apply did not execute.
Outcome
Attacker remained untrusted.
KINE V2 contract
0x5d83f43E31Db0C3766033129d3116635dD9CB21D
Request tx
0x4cd0be1c961bc24da6c1c728dcc584ffad1b2e921d8bc8be3a275ae05cecf53d
Veto tx
0xc3ed80bf628123f0cea37017f16ba48de30377d08255002a1bec21d23017f607
Post-timelock proof: after the delay window matured, the veto persisted and the apply attempt reverted with KINE_CONSTITUTION_CHANGE_VETOED. The attacker remained untrusted.
Drain prevented
8Q proved an owner-signed unsafe Sepolia drain attempt to an untrusted recipient did not execute in the governed proof path.
Expanded matrix
8T tested unknown recipient, blocked recipient, high-value delay, untrusted calldata quarantine, panic-mode block, and trusted-recipient allow paths.
Time-lock delay
8V showed a 3600-second constitution delay where risky weakening could be requested but not applied early.
Guardian veto
8X showed a 7200-second veto window where guardian veto kept the attacker recipient untrusted in the governed route.
Read-only hosted beta
The website can connect to supported wallets for public context and preview decisions. It does not take custody, request seed phrases, or move funds from the read-only path.
KINE enforcement path
Full protection requires assets or execution to pass through the KINE smart-account constitution, where policy can allow, delay, queue, pause, quarantine, or veto execution on the governed route.
KINE V2 was deployed on Sepolia testnet and tested against a dangerous constitution change. The owner authority requested a risky trusted-recipient weakening, the guardian vetoed it, and the attacker address remained untrusted after the apply attempt.
1. What happened?
A valid owner-authorized request tried to add a risky trusted recipient.
2. Why did KINE intervene?
The request would weaken the account constitution, so it required governance and veto review.
3. Who stopped it?
The Guardian-bound constitution vetoed the pending constitution change before it could become a trusted rule.
4. What proves it?
Sepolia contract, request transaction, veto transaction, local receipt, report, and locked Git commit.
Safe public claim
On Sepolia testnet, KINE V2 demonstrated that owner authority can request risky constitution weakening, guardian authority can veto it, and the attacker recipient remains untrusted after the apply attempt.
Truth boundary
This is a Sepolia testnet proof for one tested scenario. It is not audited, not mainnet protection, not production infrastructure, and not a real-fund safety guarantee.
Start here to understand KINE, then inspect the governed proof evidence and current edition availability.
Review governed proof evidence
Review the 8X Sepolia live veto proof: contract, request transaction, veto transaction, apply attempt blocked, and attacker not trusted.
/receipts
Review editions and availability
Compare the cumulative product editions and the current public-beta, Alpha, and proof-path boundaries.
/pricing
Four protection layers
Each layer reuses the same governance model, but its protection level and delivery boundary remain distinct.
Read-only wallet inspection, Action Review, Guardian monitoring, History, and Supporting Evidence.
Read-only observation and signing-context warnings on the approved browser scope. No interception or blocking.
A local TypeScript Alpha contract prepares canonical KINE intelligence and handoffs. It is not a production remote service.
Verified Sepolia Safe / ERC-4337 proof path and deterministic lifecycle contracts for supported routed assets and actions.
Principle
Key Is Not Enough + Intent Is Not Enough = Execution must pass KINE governance.
Truth boundary
Ordinary wallets receive inspection, intelligence, and supported warnings. Enforcement applies only to verified assets and actions routed through a supported governed account. Mainnet production enforcement is not certified.
Key Is Not Enough
A private key can authorize a transaction, but a key alone does not prove safety, intent, consequence, or governance approval.
Key = Authority = Execution
Key + Governance = Protected Execution
1. Intent
User initiates
2. Preview
Simulate outcome
3. Classify
Risk assessment
4. Govern
Policy enforcement
5. Execute
Receipted action
"Private keys prove control, not safety. Before you sign, prove the consequence."
In traditional wallet security, possession of a private key equals absolute control. If a key is compromised, funds can be drained instantly and irreversibly.
KINE introduces a governance layer between signing and execution. On routed actions, policy can deny, delay, queue, pause, or veto unsafe transactions before funds move.
Real-world exposure scenarios
Threat
Private key visible during screen share for 3 seconds
KINE Action
Governed-route review is required. Unsafe execution can be denied, delayed, queued, paused, or vetoed.
Threat
Seed phrase accidentally shown in YouTube tutorial
KINE Action
Governed-route review is required before supported transfers continue.
Threat
Private key committed to public repository
KINE Action
Threat review is recorded. Governed-route denial can apply to drainer-like interactions.
"A valid signature should not be enough to drain a wallet. Execution must be previewed, classified, governed, and receipted."
A private key proves you want to do something, but not that you should do it. Signing authority and execution permission are separate concerns.
Every transaction must be simulated in a sandbox to reveal its true consequences before irreversible execution on-chain.
Use threat intelligence, attack corpus, and pattern analysis to classify every transaction's risk level before allowing execution.
Policy rules determine whether a transaction should execute, even if the signature is cryptographically valid.
Key compromise detection must trigger a governed response, but only routed actions can be denied, delayed, queued, paused, or vetoed by policy.
Governed decisions should produce a structured record showing what was evaluated and which evidence supports the result. The current beta is not an immutable production audit vault.
The KINE Standard can be implemented at different layers of the wallet security stack:
Use the local KINE SDK Alpha contract to inspect supported action context and prepare a canonical handoff. Ordinary SDK inspection does not enforce or block wallet execution.
Deploy KINE as an RPC proxy only where a supported integration explicitly routes requests through governance before execution.
Implement KINE governance in smart contracts for routed actions, with on-chain policy enforcement and multi-sig or owner coordination where supported.
Run KINE at the treasury infrastructure level only for routed and certified execution paths, not as a blanket claim over every broadcast.