~
Docs
CoursesLanguageSystemUserspaceToolsManualGlossary
AgentAmesAPIAquaArmArvoAtomAuraAural ASCIIAzimuthBatteryBehnBowlBridgeBuntCardCaseCaskCellCensuresClaimsClayCold atomCometCommitConsContextCordCoreDelegated SendingDeskDillDocument ProposalDojoDoorDouble-bootDry GateDuctEclipticEntropyEvent LogEyreFaceFactFoo Bar BazGalaxyGallGardenGateGeneratorGiftGlobHD WalletHelmHoodHoonInvite TreeIrisJaelJetKelvin versioningKernelKeyfileKeywordsKhanKilnLandscapeLegLickListLoobeanLullMarkMetalsMoldMonadMoonMoveNockNoun~OTA UpdatesPath PrefixPath@pPayloadPeekpHPierPillPlanetPokeProxiesScryReplayFactory ResetRollerNaive rollupsRuneRuntimeSailSampleScrySenateShipSlamSpiderSponsorStarStringSubject Oriented ProgrammingSubjectSubscriptionTapeThreadTrapUdonUpgrade ProposalUserspaceVaneVaseVereVotingWarm atomWet GateWingWireWrapper~zodZuse
Glossary/Delegated Sending

Delegated Sending

The Delegated Sending Azimuth contract is a way that a star distributes L1 planets. After a star configures the Delegated Sending contract as its spawn proxy it can give invites to planets, and those invitees can subsequently send additional planets from that star to their friends, and pass on this invite power indefinitely. This contract keeps track of those operations in the form of the Invite Tree, so the relationship between inviters and invitees is publicly known.

With the introduction of the L2 invite system, delegated sending is less commonly used.

~Urbit Docs
HomeCoursesLanguageSystemUserspaceToolsManualGlossary
GitHubAirlock APIsUrbit BinariesDeveloper Mailing ListIssue TrackerWhitepaper
Privacy Policy
Terms of Service
support@urbit.org