Magicblock
Repository viewer
Legacy docs parity surface
Back to repository viewer
Repository document

MagicBlock Private Payments Live Probe

magicblock/private-payments-live-probe.generated.md

Boundary

This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.

Open raw file

MagicBlock Private Payments Live Probe

Generated: 2026-05-23T02:52:23.193Z

This packet verifies the MagicBlock Private Payments lane used by PrivateDAO without printing signatures, bearer tokens, private balances, or private keys.

Capability Matrix

GroupStatusReason
Private Payments healthusedThe probe checks https://payments.magicblock.app/health and the PrivateDAO read-node health proxy.
Challenge/loginused for readinessThe probe requests a challenge for a public test wallet. It does not sign or print bearer tokens.
Private balanceauth-boundPrivate balance reads require a bearer token from the wallet-signed challenge/login flow.
Unsigned transaction buildersavailableDeposit, transfer, and withdraw builders are wired in repo code; live signing/submission remains wallet-side.
Ephemeral Rollup regionsusedThe probe reads the MagicBlock status API and records live devnet services for reviewer evidence.
MagicBlock Dev SkillinstalledThe skill is installed under ~/.codex/skills/magicblock and was used to align the challenge/login and bearer-token boundary.

Live Results

  • MagicBlock docs index: ok
  • Payments API health: ok
  • PrivateDAO read-node MagicBlock health: ok
  • Direct challenge readiness: ok
  • PrivateDAO challenge proxy: ok
  • Devnet USDC mint initialization check: ok

Devnet Region Status

RegionLiveServices
devnet-as.magicblock.appyeser:live, rpc_router:live, pricing_oracle:live, vrf_oracle:live
devnet-eu.magicblock.appyeser:live, rpc_router:live, pricing_oracle:live, vrf_oracle:live
devnet-tee-as.magicblock.appyeser:live, vrf_oracle:live, rpc_router:off, pricing_oracle:off
devnet-us.magicblock.appyeser:live, rpc_router:live, pricing_oracle:live, vrf_oracle:live

Auth Boundary

MagicBlock private balances require the challenge -> wallet signature -> login bearer-token flow. PrivateDAO exposes challenge initiation through /api/v1/magicblock/challenge?pubkey=<wallet>, but does not fetch private balances without Authorization: Bearer <token>.

The Payments API returns unsigned transactions for deposit, transfer, and withdraw flows. The user wallet must sign and submit them to the returned target connection.