Creating Tokens on Monero (XMR) Using Coded Inputs, Pseudo-Treasuries and Distributed Bots Secured by DRM Software.

The system described in this post is called "Peng(e)".

Creating tokens on Monero will require three things;

  1. Coded inputs
  2. Pseudo-Treasuries
  3. Distributed Bots

Coded Inputs

These are specific amounts of XMR sent to an address controlled by network bots, this amount is an instruction which uses the last (5) decimals of a Monero input.

I.E. if *unknown address* > sends *amount* then > execute *corresponding action*

In the above example the user sent 0.000000028100 which is coded as 0.0000000###00 or "Withdraw". The first three numbers are a random code required by the web bots when initiating a transaction which allows them to tell transactions apart easier.

However, before the user can initiate any transaction they must provide a "proof", which means they are issued a code that must be signed alongside their transaction input, each Pseudo-treasury is coded to a specific public key, this is the public key that created the account, ownership of a public key can be proven using a digital signature.

Pseudo Treasuries

These are public keys managed by network bots, each Pseudo Treasury is owned by a specific user and can hold up to (4) tokens. Each token is a Pseud-Key of its own, the token balance is stored in an "internal Ledger" which is just a json directory where the token's balance is written as seen in the earlier image. Alongside this will be "Token registries" which are also json directories. The way these two directories work is that a user's json entry is coded with Token# i.e. Token1… Token2… Token3…. Each of these is then "activated" when they first buy a token, the token registry then gets updated to show that it now has a new user and that the token is stored in Token slot #. So all future buys or sells will be treated in the same way.

The above image is a blank example of this, each token registry get continuously updated until there are 100 tokens each with 100 addresses, at which point a new registry is created.

Tokens are swapped using single sided liquidity, this means the price is enforced by the bots rather than a constant market algorithm ( I expand more on these concepts here, it is very long). But what this means is that when a user wants to buy a token; XMR is transferred from their Pseud-key and sent to the token's address, this becomes part of the liquidity and can affect price if the token is set to have a floating price. Price itself is a value that is ascribed to each token and is changed based on direct buys or sells, I also expand on why existing swap mechanisms on EVMs chains is faulty in my TeF article above. Note that because input amounts are not knowable on Monero, TeF-XMR is calculated using the block reward amount divided by 1,000,000 and inverted, this becomes 1TeF,

Reward per block is an indicator of on-chain activity which in turn is an indicator of demand or price, reward per block can be used as TeF to denote the value of the chain against the overall commodities market. This data must be inverted to get the opposite of the chain's value in the pairing, which is; the TeF or value of commodities as a whole against the chain.

Distributed Bots

The webview as seen in the spoof sample above and every other aspect of the system is hosted by a distributed network of bots, anyone can join and host a node, this network is in turn protected by a DRM software known as HYPR, HYPR simply takes control of the Node operator's computer at root level and changes permissions for the network files, making itself the only one allowed to read/write the files, each time the computer is booted HYPR is booted along with it and executes a simple taskbar launcher which the user can use to start the bot or turn off the bot. Further protections for HYPR are explained in my design for Peng(a); a version designed to best compliment Bitcoin (BCH), as opposed to Peng(o) for Bitcoin (BTC). These files can be found on my Medium.

Additional Information

Another concept that Peng incorporates is float values, floats are very important for creating liquidity, this is because the coin of any chain already has float values i.e. 999999999999.999999999999 the float is the decimal, if a token system does not have decimals it is impossible to create a liquidity pairing because only 1 or more of the token can ever be bought.

I will conclude the post here, but I do require assistance with implementing Peng, if you have any criticism or recommendations please let me know below.

submitted by /u/Elix_Exo1127
[link] [comments]

Leave a Reply

Your email address will not be published. Required fields are marked *