Package sugarproxy holds the rules of sugar proxy (sugar repo, PROXY.md): which sites sharers' home connections may carry, for which customers and why; which app releases they may run; which hubs they may connect to; who pays them. Sharers' apps read these rules through a light client, from one parameter this realm writes on every change (params "doc": the canonical JSON of everything below), so no hub can change what a sharer's connection does.
Who decides:
- Holders of the SUGAR token, through kourt's governor (govern.gno): they add and remove anything.
- A delegate realm, if they name one (gno.security's, say): it adds and removes sites, nothing else.
- GovDAO (govdao.gno), above both: it adds and removes anything at once, vetoes, pauses, and names the delegate and the guardian. A guardian it names (the deployer, at first) may veto and pause, never approve.
Anything added by the token or the delegate waits out a veto window before it counts; GovDAO's own additions count at once. A veto or a removal counts at once, whoever makes it.