Aramid Finance's Soldier-node bridge processed 5,414 cross-chain transfers in nine months

The corridor between Voi and everywhere else

Voi Network launched its mainnet in September 2024 as an Algorand-family (AVM) chain, inheriting the technology but not the DeFi liquidity that had already built up on Algorand itself. Aramid Finance¹ stepped into that gap with a decentralized bridge: rather than a single operator holding the keys, a distributed set of signers called Soldiers processes every transfer, and the homepage states that every bridge request 'must be signed by a majority of nodes from a peer-to-peer, decentralized relay network.'

The protocol describes itself as a decentralized cross-chain protocol spanning the AVM chains Algorand and Voi plus the EVM networks Arbitrum and Base; Ethereum appears in its network list but is marked inactive, and the documentation also references NEAR even though the published list of supported networks does not include it. Aramid has been around since February 2022, when it announced a testnet bridging Algorand with Ethereum and Polygon, and it became the reference gateway for Voi after that chain launched: the Voi Foundation's staking guide tells users who hold wrapped VOI elsewhere that they 'must use the Aramid Bridge to bridge them back to the Voi network.'

The project is maintained by the Aramid Collective — described in its documentation as a non-profit — and governed by the Aramid DAO, with Soldier Nodes serving as voting members.

How a transfer actually works

Aramid uses a lock-and-release model. Send USDC on Base to the bridge contract and, once the Soldiers confirm the lock, the bridge issues 'Aramid USDC' on Voi — a wrapped version of the stablecoin that can be spent in Voi DeFi. Reversing the route returns the original token. The current app defaults to exactly this path (Base USDC in, aUSDC out on Voi), and inspecting the app's network calls confirms it is wired to a mainnet API rather than a testnet.

The user-facing mechanics differ by direction, and they determine how much work the recipient has to do:

The AVM side carries Algorand's opt-in requirement: accounts must register for each token before they can hold it, which is why the bridge app checks the destination address and warns before a transfer. The docs give recipients 1,000 blocks after bridging to complete the opt-in.

Soldiers, not a single signer

Under the hood, Aramid is closer to a distributed validator set than to a traditional bridge multisig. Soldier Nodes monitor lock transactions on the source chain, validate signatures from other Soldiers, and submit the release transaction on the destination chain once enough signatures accumulate. The docs describe N-out-of-M multisignature validation with no single node able to approve a transfer, plus ECDSA signatures and SHA-256 hashing for the messaging layer. Soldiers communicate over an Algorand-based application-specific chain the docs call AramidMain, with a libp2p-based backup protocol.

The on-chain record supports that picture. The Algorand bridge account currently holds roughly 56,800 ALGO and 30 assets, and its signing authority has been rekeyed to a separate dedicated address — an arrangement consistent with the multisig design documented by the project. Governance contracts allow adding or removing Soldiers and adjusting signature thresholds, and the smart contracts use a proxy pattern so upgrades do not force users to migrate. The docs state that the protocol undergoes third-party security audits and continuous automated testing with tools such as Slither and Mythril; no specific audit report is currently linked on that page.

Fees and practical details

Aramid charges a 0.1%² baseline fee on all bridging transactions, with a hard minimum floor of roughly 0.0999%³ (the transferred amount divided by 1.001); specific routes can configure a higher minimum through a percentage and/or a constant component, and all fee arithmetic truncates rather than rounding up. Users also pay ordinary network gas fees on both the source and destination chains. The docs say transfers typically complete in under three minutes and publish both the AVM and EVM bridge contract addresses so users can verify where they are sending funds.

Nine months of usage data

In June 2025 the project published a metrics report for the Voi bridge covering September 2024 through May 2025. It is the project's own accounting rather than an independent audit, but it is unusually specific. Headline figures: 5,414 transactions, 307 unique wallets, and 67.4% of users making more than one transfer. Monthly VOI activity:

Source: 4 docs.aramid.finance

Selected asset detail from the same report, using the report's own USD estimates (aUSDC pegged at $1.00, VOI around $0.0013, values dated to the report). The headline total of 5,414 includes a few additional tracked assets beyond these seven:

Source: 5 docs.aramid.finance

The pattern is a long tail: VOI, Aramid USDC and Unit account for nearly all the recorded value, while memecoins and governance tokens appear in single-digit transfer counts. What the report does not show is deep secondary liquidity. On Algorand's DEXes today, Tinyman lists Aramid VOI with about $2,963 of liquidity and roughly $35 of 24-hour volume, and Pact's pools for Aramid USDC currently show zero dollars of TVL. The bridge moves real value, but the wrapped assets it mints remain niche instruments outside the corridor itself. The Algorand bridge account, for its part, still receives transfers as of this writing, so the protocol has not gone quiet.

An open project with an agent-ready protocol

Aramid's code and documentation are public: the AramidFinance GitHub organization holds six repositories — the docs repo was last pushed on August 2, 2026, and the bridge frontend on July 8 of that year, with Ludovit 'scholtz' Scholtz the main frontend contributor and Wild-er the main docs author. Algorand Foundation xGov records list Scholtz as product owner and identify him as the builder behind VoteCoin, A-Wallet, Stabilitas and ASA.Gold in the broader ecosystem.

In July 2025, a Medium post by Dustin requesting a 50 million VOI retroactive grant for the bridge noted that the team had 'already built and deployed the bridge (live since September 2024).' The outcome of that proposal is not documented in the materials reviewed here.

The most distinctive recent addition is a developer guide, pushed in August 2026, for integrating AI agents with the bridge. It publishes machine-readable chain and token configs, per-route fee tiers that can change by round, and the exact JSON message schema the Soldiers parse. It is also unusually candid about limits: the guide warns that soldier code does not itself verify whether the destination bridge holds enough liquidity before accepting a transfer, so agents must run their own pre-flight balance checks or risk locking funds that cannot be released. The same docs describe cross-chain messaging for arbitrary data, aimed at use cases like governance votes that span multiple chains, and note that Algorand-to-Algorand routes currently require tokens with matching decimals.

The honest bottom line

Aramid is not a large protocol: a few hundred users, thin wrapped-asset liquidity, and a publicly proposed grant that may or may not have landed. What distinguishes it is legibility. The bridge is live, documented, and active; it is the corridor the Voi Foundation itself points users toward; its contract addresses and governance rules are verifiable on-chain; and by publishing machine-readable configs and message schemas, it has made bridging something other programs — not just humans with wallets — can call directly. Its bet is that Voi's ecosystem grows, and that being Voi's open, verifiable gateway is worth more than a one-off spike in volumes.