~
Docs
LanguageCoursesUserspaceSystemToolsManualGuidesOverviewReference
GlossaryAgentAmesAPIAquaArmArvoAtomAuraAural ASCIIAzimuthBatteryBehnBowlBridgeBuntCardCaseCaskCellCensuresClaimsClayCold atomCometCommitConsContextCordCoreDelegated SendingDeskDillDocument ProposalDojoDoorDouble-bootDry GateDuctEclipticEntropyEvent LogEyreFaceFactFoo Bar BazGalaxyGallGardenGateGeneratorGiftGlobHD WalletHelmHoodHoonInvite TreeIrisJaelJetKelvin versioningKelvin versioningKeyfileKeywordsKhanKilnLandscapeLegListLoobeanLullMarkMetalsMoldMonadMoonMoveNockNoun~OTA UpdatesPath PrefixPath@pPayloadPeekpHPierPillPlanetPokeProxiesScryReplayFactory ResetRollerNaive rollupsRuneRuntimeSailSampleScrySenateShipSlamSpiderSponsorStarStringSubject Oriented Progr...SubjectSubscriptionTapeThreadTrapUdonUpgrade ProposalUserspaceVaneVaseVereVotingWarm atomWet GateWingWireWrapper~zodZuse
Additional
Reference/Glossary/Scry

Scry

A scry is a read-only request to the namespace of a local vane or agent. In Hoon, scries are performed with the .^ rune. Unlike other kinds of inter-vane or inter-agent communications, scries cannot alter the state of the ship or produce other side-effects. Additionally, scries are an exception to the purity of Hoon functions, and can be performed in-line. The scry interface is also exposed through Eyre, the web-server vane, to web clients.

Further Reading

  • Scry reference: developer documentation of how scries work and how to use them.
Edit this page on GitHub

Last modified October 8, 2023

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