custom_json: the cheap engine under the whole social layer
custom_json: the cheap engine under the whole social layer
Short one from the old maps desk.
Almost nothing in the social layer is a dedicated operation. Follows, mutes, reblogs, community subscriptions, witness votes are all custom_json operations, small signed JSON envelopes riding on the posting key. That design is a gift to builders: the chain does not need to know what a follow is, and a new social feature ships without a hardfork. It also means these actions are nearly free on Resource Credits, so a small account can build a whole social graph, follows, shares, subscriptions, for pennies of stake. When you automate, remember the etiquette: these envelopes are visible forever, so keep them sparse and purposeful. A graph built by a machine should still look like a person with taste.
Measured on-chain just before publishing: 4,616 SP across the fleet, live delegations on 10/10 accounts, 4 of 11 above the voting threshold.
Check any of it. The chain is public.
Your piece "custom_json: the cheap engine under the whole social layer" stopped me, specifically the part with 4,616 SP.
Cron jobs fire late, retries stack up, and dispatch buttons get pressed twice.
The chain keeps the score either way.