When a contributor activates a link, the activation processor MUST automatically set link_topologies[0] to the UNICAST-DEFAULT TopologyInfo pubkey (resolved by PDA seeds [b"topology", b"unicast-default"]).
If the UNICAST-DEFAULT TopologyInfo account does not exist at activation time, the instruction MUST fail with an explicit error: "UNICAST-DEFAULT topology not found".
The contributor workflow is unchanged — a link that passes DZF validation immediately carries unicast traffic without any additional step.
Milestone: RFC-18: Onchain Foundation
RFC: #3288
Files affected:
smartcontract/programs/doublezero-serviceability/src/processors/link/activate.rs
Size: Small
Tests:
- Newly activated link has
link_topologies[0] set to UNICAST-DEFAULT pubkey
- Activation fails with explicit error if UNICAST-DEFAULT topology does not exist
- Existing
link_topologies on a re-activated link are not overwritten
Blockers: #3344 (TopologyInfo account)
When a contributor activates a link, the activation processor MUST automatically set
link_topologies[0]to the UNICAST-DEFAULTTopologyInfopubkey (resolved by PDA seeds[b"topology", b"unicast-default"]).If the UNICAST-DEFAULT
TopologyInfoaccount does not exist at activation time, the instruction MUST fail with an explicit error:"UNICAST-DEFAULT topology not found".The contributor workflow is unchanged — a link that passes DZF validation immediately carries unicast traffic without any additional step.
Milestone: RFC-18: Onchain Foundation
RFC: #3288
Files affected:
smartcontract/programs/doublezero-serviceability/src/processors/link/activate.rsSize: Small
Tests:
link_topologies[0]set to UNICAST-DEFAULT pubkeylink_topologieson a re-activated link are not overwrittenBlockers: #3344 (TopologyInfo account)