Providers
Turbo
Arweave through turbo-gateway.com, the AR.IO gateway whose index still has 2019. First pick for Arweave. No key.
Provider
Turbo
- arweave
- Chains
- 1
- Auth
- none
- Operations
- 4 of 10
served 4 / 10
Operations
- balance
getBalanceserved - history
getTxHistoryserved - tx detail
getTxDetailserved - utxos
getUtxosabsent - pubkey
getPubkeyabsent - contract
getContractInfoabsent - tokens
getTokenBalancesabsent - transfers
getTokenTransfersabsent - gas
getGasDataabsent - block
getBlockInfoserved
Access
- Create
create("turbo") - Import
@agntn/explorers/providers/turbo - Host
turbo-gateway.com - Statusproviders on the docs worker
Address it
import { Turbo } from "@agntn/explorers/providers/turbo";
const turbo = new Turbo(); // or create("turbo"), or no provider at all on Arweave
await turbo.getTxHistory("PbdTDYikdddWfNFlDt2aZokALXKe1mJVSC9TALUBNv8", "arweave", { sort: "asc" });
That wallet got its first AR in May 2019. arweave.net starts its history years later. Turbo starts on the right day.
Why first?
AR.IO's own docs call this index comprehensive, and for layer 1 transfers it is. Old wallets, tagged posts from those first years, all there. So an Arweave read without a provider lands here first. Does it fail with a 5xx or a timeout? The read moves to ar.io once.
Gotchas
- Some bundled data items from around block 1,700,000 never made it into this index. ar.io has them.
- It's the same class as arweave.net, only the default gateway differs. Windows, tags, fees and pending rows behave as listed there.
- Data items carry their real bundle id in
raw.bundledIn, where arweave.net leaves it empty.
Where it lives
src/providers/turbo.ts, on top of src/providers/arweave.ts.