HiveRemit · cross-border remittance, attested

Travel-rule-compliant remittance, on USDC, in seconds.

Every cross-border transfer carries a Hive-attested identity receipt on both the originator and the beneficiary. FATF Travel Rule, US BSA, EU TFR, MAS Notice 626, and FinCEN expectations satisfied as a side effect of the receipt rail. The remittance corridor that an MSB, a bank, or an institutional originator can legally clear at scale.

Why this exists

Cross-border remittance is a multi-billion-dollar-per-day flow that legacy stablecoins handle informally and that regulated institutions cannot legally touch at scale. The reason is identity: FATF Travel Rule, US BSA §1010.410(f), the EU Transfer of Funds Regulation, and equivalents in Singapore, the UK, the UAE, and India all require originator and beneficiary identity to travel with the funds. Stablecoin rails today do not carry identity in any standard way. HiveRemit binds Hive-attested identity to both ends of every USDC remittance, in a CBOR-canonical receipt that every counterparty can verify offline.

What HiveRemit attests

Every cross-border remittance carries a dual-signed (Ed25519 + ML-DSA-65) post-quantum-ready receipt with travel-rule identity on both ends. The 10 attested states under HiveRemit:

01
originator_attest — sender identity verified, KYC tier signed, beneficial owner declared where required.
02
beneficiary_attest — recipient identity verified by the receiving institution, signed at the boundary.
03
corridor_screen — the corridor is screened against sanctions, PEP, and high-risk jurisdiction lists. CLEAN-MONEY gate clears.
04
purpose_bound — the purpose of remittance is declared and bound to the receipt. Family support, B2B invoice, payroll, charitable — each typed.
05
fx_locked — the executed FX quote is bound to the action with rate, venue, and timestamp.
06
travel_rule_payload — the FATF travel-rule message is generated, signed, and routed under the receiving institution's preferred protocol (Sumsub TRP, Notabene, TRISA, GTR, OpenVASP).
07
settlement_init — USDC movement begins on Arc. Receipt opens.
08
settlement_final — USDC arrives. Settlement receipt closes. Beneficiary institution acknowledges in-band.
09
fiat_off_ramp — beneficiary off-ramps to local fiat. The off-ramp leg is bound to the original receipt id.
10
regulator_export — the full chain-of-custody is exportable to either regulator on either side of the corridor, dual-signed and offline-verifiable.
Built for USDC on Arc

The remittance corridor a regulated institution can actually run.

HiveRemit settles in USDC on Arc with sub-second finality and identity-bound receipts on both ends. Every corridor a bank, MSB, or institutional remitter operates becomes legible to its supervisor on demand. Tether-denominated corridors do not have this property and cannot acquire it under their current structure. USDC + Hive does.

Who runs on HiveRemit

Pricing

$0.0096
Per attested event
Standard tier. ~$0.10 per typical 10-event corridor cycle. Settlement in USDC on Arc.
$0.0192
Per event · Regulated
Regulated tier. Travel-rule message routing, sanctions screening, regulator export portal.
$4,999
Per month · Unlimited
Flat-rate enterprise tier for MSBs, payroll providers, and platforms. White-label available.

Why now

A direct conversation, not a procurement cycle

If you run a remittance product line, a corridor desk, a payroll platform, or a regulator-facing institution and you want the travel-rule problem solved at the receipt layer, the fastest path is a direct note. Steve reads them.

Live since 2026-05-18 · Dual-signed (Ed25519 + ML-DSA-65) · FATF Travel Rule / US BSA / EU TFR / MAS 626 / EU AI Act aligned · Settles USDC on Arc and Base 8453