Structural pre-sign intelligence for autonomous wallets.
VNSIS Argus Protocol is a graph-based pre-sign decision system developed by VNSIS Technologies Limited. It evaluates a proposed transaction's counterparty — and the controllers, dependencies and provenance standing behind it — before execution.
Clean in front, risky behind
Screening resolves the address in front of you. It does not resolve who deployed it, who can still change it, or what it leans on at execution time. Step through the same assessment Argus performs.
The platform
Argus is not four products. A transaction is decoded once, evaluated against structure and evidence once, and resolved by one versioned policy into one verdict — the receipt is simply that decision, made durable.
Deterministic, versioned verdicts over a canonical transaction. The same intent, policy and evidence always produce the same decision — and the policy version that produced it travels with the result.
Deployers, controllers, proxy implementations and dependencies, traversed as a graph. Risk that a counterparty inherits is reported as inherited, never blended into its own record.
Evidence carries its own state. Missing, stale or unavailable intelligence is represented as exactly that, so an absent check can never be rendered as a clean result.
An optional signed record binding the assessed payload, the policy, the disposition and a commitment to the reasoning — so a decision can be re-examined after the fact.
Decision Receipt
A receipt binds one assessment to the exact payload it was made against, the policy version that produced it, the coverage it relied on and a commitment to its full reasoning. Change any of those after the fact and verification fails.
Illustrative offline fixture. Nothing here represents an operational screening result.
Receipt issuance is optional at the gate.
A fixture-signed receipt cannot invoke an execution port.
Where it fits
Agents sign faster than anyone can review structure. Argus answers the relational question before the signature, not after the incident.
Machine-initiated payments to counterparties nobody vetted by hand, bounded by policy that has to be explainable to a risk function.
High-volume transfer paths where an address-level allowlist is the only control standing between an agent and an unknown dependency.
Platforms that execute on behalf of others and need a defensible, versioned reason for every transaction they let through.
Ecosystems
The decision engine holds no chain knowledge. Ecosystem adapters, intelligence sources and execution integrations all sit behind contracts at the boundary — so a new chain or a new provider is an implementation, not a rewrite, and the decision and its reasoning look the same on either side.
Exact ERC-20 decoding, EIP-1967 controller discovery and a Circle Wallets pre-sign gate, all implemented and tested against injected transports and a fake port. No live Arc endpoint is configured and no Circle execution has been performed.
Arc implementation status →The graph model and adapter seams that the Sui work is built on exist and are tested. Programmable-transaction-block pre-sign decoding is not implemented, so there is no complete Sui screening path today.
Sui implementation status →Complementarity
Executes the transaction and holds the wallet and key infrastructure. Argus never signs, broadcasts or holds a key.
Provides direct compliance and address screening where available — the preferred source of direct-match evidence, not a capability Argus duplicates.
Contributes structural, controller, dependency and inherited-risk evaluation, and binds the decision to the execution-relevant payload and policy.
No Circle integration is live today, and nothing here represents an endorsement or a commercial relationship with Circle.
Who builds this
Systems · Infrastructure · Security. Argus is built by Evans Isioma Obi, Founder & CTO and sole builder — a background in cybersecurity, application security and infrastructure engineering applied to the one question wallet controls still cannot answer.
Argus is pre-production and in active development. If you run autonomous execution, integrate wallets, or evaluate ecosystems, the useful conversation starts now.