Good day,
This is an application to @deathwing for another Claude application. It ends on 30th April, and I want to proactively apply so I don't get downtime.
I am going to include the GitLab stats on what I have been working on for Hive. Please note that while the repos here are open-source on https://gitlab.syncad.com/hive/, they are far from ready. This is across 14 days. Special thanks to @blocktrades for creating the repos and to @gandalf for the runners in the pipeline (they have been a super value-add).
Headline numbers
Commits 1,501 Lines added 186,329 Lines deleted 13,476 Net +172,853 Active window 2026-04-11 → 2026-04-25 (~14 days) Pace ~107 commits/day · ~13k LOC/day netPer-repo breakdown
Repo Commits Lines+ Lines- Net First Last velocity 478 47,581 2,806 +44,775 Apr 11 Apr 25 velocity-bridge 226 34,137 4,277 +29,860 Apr 14 Apr 19 velocity-bridge-ui 148 40,848 5,049 +35,799 Apr 19 Apr 25 velocity-identity 326 20,375 351 +20,024 Apr 22 Apr 25 velocity-js-sdk 144 15,606 266 +15,340 Apr 24 Apr 25 velocity-unity-sdk 93 6,145 70 +6,075 Apr 17 Apr 17 velocity-wallet 86 21,637 657 +20,980 Apr 23 Apr 25Tangible results??
I have managed to complete a bridge between Hive-Engine to Solana and back
H→V→S round trip — 2026-04-19
First end-to-end live run with all three chains on the happy path.
A user on Hive publishes a real tokens.transfer to the bridge
vault; velocity auto-mirrors and re-emits a BridgeOut; Solana
devnet mints wrapped STELLARUM. One user action, four on-chain
transactions, ~3.7s wall-clock from Hive detect to Solana confirm.
Setup
- Sender account (Hive):
spiritsurge - Vault account (Hive):
velocity-bridge - Velocity namespace/token:
astralwars/STELLARUM - Solana recipient pubkey:
21YhDTgH86WQKsDm4gEsFsARuwoQ3HppSqfi4GeaYvgc(devnet) - Token mint (Solana devnet):
2K1eWptkN3zmd5oCLSfLuFYsBUwBiHUYHpgY9WqghvHf - Relayer commit:
fe1131b - Memo form:
velocity:solana:
What I did
One action. From spiritsurge on Hive, a real HE tokens.transfer
of 24 STELLARUM to velocity-bridge with memo:
velocity:solana:21YhDTgH86WQKsDm4gEsFsARuwoQ3HppSqfi4GeaYvgc
That's it. The rest is automatic.
[IMAGE: images/01-hive-op.png]
What the bridge did
Leg 1 — Hive: real HE transfer (spiritsurge → velocity-bridge)
- Tx id:
f6b7358444a746ea61254d03e31dfe25068c8112 - Block: Hive 105649098
- Op:
custom_jsonwithid=ssc-mainnet-hive,contractName=tokens,
contractAction=transfer. Signed underrequired_auths(active),
since HE rejects tokens.transfer signed with posting authority. - Vault balance on Hive-Engine credits 24 STELLARUM. Relayer's
deposit watcher picks up the op at confirmation depth 3.
Leg 2 — Velocity: BridgeIn credits hive-transit
- Block: velocity height 3723
- Action:
BridgeIn { source_chain: "hive", source_tx_id: <20 raw bytes of Hive tx id>, to: "hive-transit", amount: 24, ... } - The
hive-transitaccount isn't pre-registered; velocity
auto-creates accounts on first BridgeIn. By design it never
accumulates balance — the next leg debits the same 24.
[IMAGE: images/02-velocity-bridge-in-block-3723.png]
Leg 3 — Velocity: BridgeOut auto-hop from hive-transit → Solana
- Block: velocity height 3724
- Event hash:
8cbd0494d8c240542c33bf4b5fc43563e601cacc96e1e16c5f66860060e798b1 - Action:
BridgeOut { from: "hive-transit", amount: 24, destination: <32-byte Solana pubkey>, ... } - Immediately after the BridgeIn, the relayer's hive watcher POSTs
/bridge-outto velocity with the Solana destination parsed
from the memo. Velocity signs + emits the event; the forward-leg
pipeline picks it up through the SSE stream.
[IMAGE: images/03-velocity-bridge-out-block-3724.png]
Leg 4 — Solana devnet: mint 24 wrapped STELLARUM
- Signature:
5wQeAC4mppDkfPJU622LGfx5QezaHN9gx6TusM6jtUCxsRgC9uPcnJsvGEThagWGLBdgNbEpwk6P2CbMVd93vteNyou can click on the link here to view it on solana explorer. - Mints to the recipient's ATA for the STELLARUM mint. Memo
instruction on the same tx carries the human-readable
velocity-bridge: mint 24 STELLARUM to 21YhDTgH...line.
[IMAGE: images/05-solana-memo.png]
Status endpoint correlation
GET /bridge-out/8cbd0494.../status on velocity returns the Solana
side of the hop without the UI having to touch a Solana RPC:
{
"event_hash": "8cbd0494d8c240542c33bf4b5fc43563e601cacc96e1e16c5f66860060e798b1",
"status": "minted",
"destination_chain": "solana",
"destination_tx": "5wQeAC4mppDkfPJU622LGfx5QezaHN9gx6TusM6jtUCxsRgC9uPcnJsvGEThagWGLBdgNbEpwk6P2CbMVd93vteN",
"confirmed_at_unix": 1776578437
}
[IMAGE: images/04-bridge-out-status.png]
Timing
Event Timestamp (UTC) Hive block 105649098 produced ~06:00:30 Relayer detects deposit op 06:00:34.237/bridge-in credits hive-transit (velocity block 3723)
06:00:34.549
/bridge-out emits event from hive-transit (velocity block 3724)
06:00:34.550
Solana mint_from_proof submitted
06:00:34.967
Solana mint confirmed
06:00:37.930
End-to-end: ~3.7s from deposit detection to Solana confirm.
There is also round trips and so on
https://gitlab.syncad.com/hive/velocity-bridge/-/blob/main/round-trip-2026-04-19-full-loop/README.md?ref_type=heads
I am not yet willing to completely divulge what this tech is and what it is meant to do. But I am making sure not to work on what @mahdiyari, who has accomplished a L1 bridge to Solana (this is an L2 bridge) or @magi.network is doing. (I will not be touching EVM)
We are all working towards the betterment of Hive. So my intention is to fill the gaps where possible. And trust me, for people wanting to build on Hive, there are many many many gaps so no need to fight over redundant gaps that everyone is trying to explore.
There is a whole section of work that has been done on my games that I am not even talking about, which is on a different gitlab.
