refactor(anonbeta1): registry-only baseline; archive Arcium bind for v2

[FwazB]

Summary

Resets anonbeta1 to the minimal Frontier/devnet registry baseline and archives the earlier Arcium beacon binding work for later revival.

What stays live:

• register_beacon: writes the BeaconRegistry PDA with operator, RNS destination hash, region code, and timestamp metadata
• heartbeat: updates last_heartbeat and heartbeat_count
• BeaconRegistered and BeaconHeartbeat events
• Plain Anchor program surface with anchor-lang only
• Program ID remains anon7uu8UtVoFgS8GCSfw2RqyphJhkN3xEjgPwznYDe

What is removed from the live program:

• Arcium beacon_bind registration path
• Private beacon registry account
• Registration fees and treasury transfer logic
• Arcium-specific errors/constants from anonbeta1

What is preserved for v2:

• Archived beacon bind instructions, state, events, constants, and circuit snapshots under archive/anonbeta1-arcium-bind/
• Revival notes in the archive README
• Existing ble-revshare and encrypted-ixs material for later payment/revshare work

Handoff Notes

Do not merge as part of this handoff unless the team explicitly wants the minimal registry-only baseline on main.

PR #3 is stacked on top of this work and adds the v2.A private relay counter. If the team accepts the private counter direction, review/merge PR #3 instead of merging this PR separately.

M4gic's review note is incorporated directionally: beacon registration fees are removed here. Follow-up design questions remain around replacing heartbeat with a last-cosign timestamp and exposing operator stats without leaking private relay counts.

[Magicred-1]

gm no need to registration fee anymore on beacons:

• Any Internet connected users is a beacon the Registry track the co-signed transactions.
• 1% on small amounts and dynamically decreases based on the transaction size volume.
• No need to keep the rns addresses since they can be rotated pretty easy which would break the data chain..
• Heartbeat is a good idea but it be replaced by a timestamp_last_cosign .. or something similar.
• Might be interesting to have stats to return to the user (beacon) such as the fees he's collected so far / the amounts of co-sign he've done so far and his LST Staking amount / Yield ..

[FwazB]

Handoff note on M4gic's review comment:

• Registration fees are removed from the live anonbeta1 registry path in this PR.
• The older Arcium/private-registration path is archived, not active.
• The heartbeat vs. timestamp_last_cosign change is still a product/protocol decision and should be handled as a follow-up, since this PR is only the registry baseline reset.
• Operator stats are addressed experimentally in PR feat(anonbeta1-v2): add operator-private relay counter #3 via encrypted private relay counts, with public events exposing only liveness/update metadata.

[Magicred-1]

GM, every account can now act as a beacon by default based on his connectivity, so there’s no longer a need for a dedicated Registry PDA.

Instead, confidential transfers should flow directly through the MXEs, with the second signer public key serving as the beacon reference within the smart contract for revenue share. This keeps the architecture leaner and removes unnecessary registry overhead.

The immediate priority should be tightening the confidential transfer flow and making the beacon signature a required secondary signer in the transaction model.

From there, we can fully concentrate on the offline-first direction of the program:

minimize on-chain coordination,
reduce dependency on centralized state lookup,
and ensure transfers remain feasible in disconnected or low-connectivity environments.

In short:

No Registry PDA
Every account is beacon-capable by default
MXEs handle confidential transfers
Second signer PK = beacon identity
Offline-first architecture becomes the primary design target as of now and since everything pass through anonmesh LXMF based network.

[Magicred-1]

- heartbeat: bumps last_heartbeat + heartbeat_count, emits BeaconHeartbeat
- BeaconRegistry account, BeaconRegistered + BeaconHeartbeat events
- 4 errors (InvalidRnsHash, InvalidRegionCode, OperatorMismatch, HeartbeatOverflow)```

Is dead code it's already handled on the anonmesh layer infra, no need for redundance on the program

The beacon co-sign txs with his Beacon keypair and broadcast them from anonmesh, the identity keypair can easily being rotated so no need to stored them onchain.

The instructions need to be totally normally encrypted and handle by Arcium MXEs..

Such as passing a confidential transfer / swap (LSTs) .. etc with the ATA target .. etc