⬛PLOT:PAGE

The frontends for all plots

Every plot will have a page. These pages will exist on the plot.page domain and initially will only show info about the block number the plot represents and the owner address. Once the owner claims the page by verifying ownership of the .plot that is mapped to the block, the page will generate a plot ID badge (including a generative image using block data) and the page will automatically update based on other plot protocol usage referencing the plot (block number) such as messages and other content and assets.

The plot page owner will be provided text to copy that is suitable for recursive inscription. The text will include the PLOT:PAGE JSON wrapper and the page code within it. You, the owner of the plot page, would choose whether or not to inscribe it. If you do, the page will detect the inscription onchain and reference it as well as directly display the inscription data (toggle) which will include an on-demand cryptographic checksum (hash validation).

Extended content displayed on plot pages (new messages and other recent content and activity) are supplemental and called from indexers on-demand.

This protocol and the backend infrastructure is under development.

The URLs for plot pages will be formatted like this:

Block Height (number):

210000.PLOT.PAGE

Name + Block Height (number):

210000.PLOT.PAGE#BITROPOLIS

BITROPOLIS.PLOT.PAGE#210000

Plot names will be indexed and paired with the block height so either format can resolve to a page and the URI fragment is optional.