Proposed addition of “price” to “terms” during an etch

[encloinc]

Hey! I wanted to know if we were to submit a PR to ord altering the indexer to do the following if it’s something that has a possibility of being approved.

The addition of a “price” field

Currently an etches “terms” looks like the following:

struct Terms { amount: Option, cap: Option, height: (Option, Option), offset: (Option, Option), }

I propose an OPTIONAL extra field “price” to be added to these terms, expressed as the following: price: Option<u128>

How the “price” field would function

Price is an integer expressed in Satoshi. During an etch, IF the price field is present the following would be added as a requirement:

For the following definition, “Etch Output” refers to the following:

The address owning the first NON-OP_RETURN transaction output of an Etch transaction or, in the case it’s provided, the address owning the transaction output specified by “pointer” of an Etch transaction:

A transaction including a runestone that is minting MUST include a transaction output transferring a MINIMUM of “price” amount of satoshi to ”Etch Output”

If there are no transaction outputs in vout that transfer a MINIMUM of “price” to “Etch Output”, the mint is ignored BUT the transaction is not considered a cenotaph and edicts are still processed.

If no price field is provided, all functionality above is ignored.

Usecase

This would create a decentralized way to create ICOs natively on Bitcoin - allowing the fungibility of Rune to be used as a mechanism to fund innovative projects on the space

Final thoughts

I leave my proposal here for feedback and if there’s interest / probability of merging or being added, I would be happy to implement in ord through a PR.

Thanks for reading :)