Bandwidth on the global synchronizer is paid for up front. The member burns CC to top its traffic balance back up — the burn is the purchase, which is why the same update also shows up in the burn feed.
Summary
Record Time:
Effective At:
Root Events:
2
Events:
18
Traffic Consumed:
18.2 KB
Migration ID:
4
Parties
2 parties
Click a party to highlight the events it acts in, signs or observes.
