Ruleset

Planet, Satellite and Hex Satellite Ruleset

planet ruleset

genesis ordiblockheight = 0 = 0.ordimap = bitcoin blockheight 779832

A valid Planet takes on the traits of the block referenced by the blockheight number.

planet claim command = ordiblockheight.ordimap

To make a claim on a block, a text inscription must be made using Ordinals Theory. The inscription must contain the ordiblockheight (based on sequential order of blocks on the chain, starting from 0), followed by .ordimap, as above. This is considered a Planet Claim. However, it is only verified as a valid .ordimap if it satisfies the full ruleset.

0.ordimap = example command to claim planet at ordiblockheight:0

This example inscription command demonstrates how you would claim Planet 0, based upon ordiblockheight 0. Be aware, a claim must be successful (see first is first).

regex validation = ^(?:0|[1-9][0-9]*)\.ordimap$

This regular expression denotes the accepted characters usable according to the standard for claiming ordimap planets. It simply means use sequential numbers only, followed by .ordimap. The only valid ordimap number beginning with 0 is 0.

planet claim = hard first is first

The planet being claimed at any time or blockheight as long as it is the first.

most recent mined ordiblockheight = # of confirmations from bitcoin blockheight 779832

Bitcoin block height 779832 contains the ordi deploy inscription and is equal to ordi blockheight 0. The most recent mapped and mined ordi block is the amount of confirmations the ordi deploy inscription has. It can be tracked here: https://mempool.space/tx/b61b0172d95e266c18aea0c624db987e971a5d6d4ebc2aaed85da4642d635735

unmined but claimed ordimap planets

Any one can claim an ordiblock from the future as long as they are first. They just have to wait until it is mined on the bitcoin blockchain for it to construct a map. Unmined claims to ordimap planets are like a preconstruction property deed.

satellite ruleset

satellite# = txindex (starting from 0)

When referring to satellite number (satellite#), we are referring to ordi transactions within the ordi block, starting from 0, which is the first transaction in the ordi block.

satellite claim command = satellite#.blockheight.ordimap

To claim a satellite, one simple appends their chosen satellite#. before blockheight.ordimap.

0.0.ordimap = example command to claim satellite 0 within planet 0

In this example, the parcel corresponding to transaction 0 (first ordi tx in the block) within Ordi Block 0 is claimed by the inscription, according to Ordimap Theory.

regex = ^(?:0|[1-9][0-9]*)\.(?:0|[1-9][0-9]*)\.ordimap$

This regular expression denotes the accepted characters usable according to the standard for claiming ordimap satellites. It means use two sequential numbers only, followed by .ordimap. The only valid transaction number beginning with 0 is 0. An invalid example would be 01.0.ordimap.

satellite# >= 0 and < total transactions in parent ordi block

The satellite number must be equal to or more than 0, and less than the total number of transactions in the parent ordi block.

planet holder address = satellite inscriber address

The planet holder address must be the same address as the satellite inscriber address.

fapping = send to self

Fapping is a term that simply means to send-to-self. It signals the confirmation of an action, or the initiation of a command within a ruleset.

fap planet to resolve all confirmed satellite inscriptions as valid/invalid (ends staking)

Once satellite inscription transactions have confirmed, the district must further be fapped. Unfapped satellites refers to when a district has not been fapped since satellites inscribed. Unfapped satellites are considered fake by the standard ruleset and indexing.

if the parent planet is sent to another wallet before fapping to confirm, any satellites created will not be verified

If the planet is sent to another wallet after inscribing its satellites, instead of the planet being sent-to-self (fapped), any unfapped parcels will be considered fake by indexing.

ordimap from the future can't create satellites because the transaction map does not exist

Because any number ordimap claim is valid if you are first, any ordimap that has not been mined can't create satellites. The future blocks transactions don't exist in present time.

satellite + hex theory ruleset

Coming soon