CS 498MC Martian Computing at the University of Illinois at Urbana–Champaign
Formally, Azimuth provides the following services:
These are mostly operated through the Bridge client.
You own your Urbit. But how can you verify this to others? And can you allow others to operate your services without betraying your ownership keys? The answers lie in the operations of Azimuth and Jael. %jael
was already discussed in Arvo I, where its role as a secret keeper was outlined.
Azimuth recognizes the Urbit Hierarchical Deterministic (HD) wallet, which stores sets of keys allowing certain operations to take place.
The most important of these are:
The management and spawn proxies are useful for hosting planet services or selling points.
~poldec-tonteg
, Will Kim ~hadrud-lodsef
, Morgan Sutherland ~hidrel-fabtel
, “UP8: Urbit HD wallet”Bridge is the premier service for manipulating the Azimuth PKI. Bridge provides the following services:
Bridge interacts with Azimuth via Ecliptic contracts, Ecliptic being the point management contract for Urbit.
You should review the core contracts, which are written in Solidity for the Ethereum Virtual Machine.
azimuth-js
provides a number of tools for managing transfers; for instance, transfers are initiated from Admin/AdminTransfer
and accepted in AcceptTransfer
If you are interested in further details, there has been extensive discussion of how to access and manage contracts automatically or manually on the urbit-dev
mailing list.
There has been some dissatisfaction with the Ethereum substrate which Azimuth currently uses. Since Azimuth is a public-key infrastructure that is only operated by Ethereum, it is possible and may become desirable to move Azimuth to a different platform, perhaps onto Urbit itself someday.
“Any Urbit PKI must fulfill a minimal set of requirements:
There have been a number of proposals in this direction, such as “planetoids” (tracked off-chain by sponsoring stars), batched transactions, etc.
~rovnys-ricfer
, Logan Allen, “Proof of Authority Urbit PKI”