- 1 Publishers
- 2 Records
- 3 Possible Network Topologies
- 4 Platforms
- 5 Influencers
- 6 Autominers
- 7 File Storage & Distribution
A unique ECDSA public key hash registered in the Open Index with a message and schema format that conforms with OIP's message protocol at the time of registering, verified by blockchain timestamp. Registering a Publisher Address is required to publish.
A publisher alias is a non unique name in the Open Index global namespace. Any number of Publishers can register the same Publisher Alias, but each Publisher can only have one Publisher Alias per Address. Registering a Publisher Alias is not required to publish. If one is not registered, a protocol wide alias recognized for all Publishers is the truncated first 10 characters of their Publisher Address.
A publisher name is a unique name in the Open Index global namespace. Registering a Publisher Name is not required to publish. A publisher name may be transferred to another party by sending a name transfer message. Publisher name registration is valid when all of the following conditions are met:
- Name registration message includes correct registration fee, as its tx-fee
- Earliest registration message of name, according to blockchain timestamp
- Registration has not yet expired, according to blockchain timestamp
Verified Publisher Name
A verified publisher name is an optional distinction, valid when all of the following conditions are met:
- Matches the real name of a rights holder with rights to the content, verified by public databases (ie, IMDB, MusicBrainz).
- A publisher name verification message is shared in at least one social media platform from an account controlled by the rights holder (Twitter, Facebook, LinkedIn, Steemit, Diaspora, Synereo).
Publisher Registration Fee
The Publisher Registration Fee is a token payment for the cost of inputting data into the blockchain, paid as a tx-fee. The fee to register a publisher address is only the cost of adding the data to the blockchain. The fee to register a publisher name is determined by the OIPWG, initially it is $1 per year of registration.
A record is valid if all the following conditions are met:
- The message and schema format conforms with OIP's message protocol at the time of publishing, verified by blockchain timestamp
- At least one file is included in the message, defined by a network name and address hash
- A correct publish fee is paid as a tx-fee
Any files included in the message are assumed to be published by a party with the right to do so, so their ownership is attributed to this publisher. If another publisher attempts to publish the same files at a later date (identifiable by the file address hash), the earlier Record is assumed to be by the rights holder, and the later Record will not be accepted.
A publishing fee is payment for the cost of inputting data into the blockchain. It is paid as a tx-fee and used to validate that a record is OIP compliant. The publish fee for free content is the flat tx-fee of the amount of data to be input into the blockchain. The publish fee for commercial content is based on a calculation that includes the commercial value of the content, and the current average cost of all commercial records published in the Open Index. Publish fees drive the security incentive; they increase the potential coins captured by miners in addition to the standard block reward. This sink (fee) is key to the system design because the index blockchain tokens must be use to publish content to the index. Also functions as anti-spam incentive (viggish footnote).
To determine that the correct amount is paid for the publish fee, the history of the tx-fee tokens are evaluated to determine if the tokens are mined, or from circulation. Tokens cycle through the system; publish fees are sent as a tx fee, adding to the standard block reward.
To verify they have not circulated on the market, tokens are considered mined when all of the following conditions are met:
- Exactly two or three transactions between a) the transaction in which the tokens were newly created or previously spent as a tx fee and mined again b) the tokens being used as the publish fee. If any more than two or three transactions, they must be change sent to self.
- The most recent transaction must be from a registered autominer to the publisher.
- The earliest transaction must be a block reward transaction.
- Specific market data must be in the coinbase as a valid historian message (rental rig cost, flo market prices)
- If there are three transactions, the second transaction must be from an OIP-compliant pool to the registered autominer and include in its transaction message which blocks the block-reward payout was for (since pools delay payouts by varying numbers of blocks).
When tokens are mined, the USD-per-FLO offer price value is determined by the cost to mine at the blockchain timestamp and the historian message in the coinbase when it was mined.
Tokens are considered from circulation if any of the conditions required to be mined are not met. When tokens are from circulation, USD-per-FLO value is calculated based on the average exchange price at the time of the blockchain timestamp when the publish attempt is made using historian data from the index blockchain.
Fee is calculated differently for free and commercial records.
If a record contains only free content, the publish fee is calculated based on the size of the index data and the cost per byte to store the message in the index blockchain.
Looked up variables:
Size of record, in bytes. Note: meta data ONLY, not file data itself.
Minimum transaction fee per byte, in Flotoshis (1/100,000,000 of a Florincoin). This will ultimately be a completely market determined rate; pools will announce their own minimum rate to confirm transactions, and an API endpoint will collect and index them. Currently, use a hard-coded value of 100
Fee to publish a free record, in Florincoins.
If a record includes any commercial content, the publish fee is a function of (1) the commercial value of the content, called the record cost and (2) the current average cost of all commercial records published in the Open Index, called the average record cost.
Looked Up Variables:
Number of files in the record.
Alexandria's hosted endpoint, returned as the json field labeled oip-041:artifact:storage:files:minPlayMinimum play price for each file in the record. Can be looked up at
Alexandria's hosted endpoint, returned as the json field labeled oip-041:artifact:storage:files:sugBuySuggested buy price for each file in the record. Can be looked up at
Alexandria's hosted endpoint, returned as the json field labeled avgArtCostThe average "cost" of all commercial records in the open index. Can be looked up at
Total of minimum play prices for all files in the record.
Total of suggested buy prices for all files in the record.
The "cost" of this record, a single value representing the average between the sum of all minimum play prices and the sum of all suggested play prices.
Fee to publish a commercial record, in US Dollars.
Possible Network Topologies
A platform is an interface (hosted or decentralized) for end users to find or discover content and make purchases. Platforms are paid a percent (defined by Publishers) of the payment activity they facilitate.
Examples: websites, smart phone apps, smart TV apps and physical kiosks.
An interface is considered a platform when either or both of the following services are provided:
- Hosting a marketplace
- Providing payment processing services
A platform is valid if all of the following conditions are met:
- Send a platform registration message with a publicly visible payment address to the Open Index, default payment address is currently BTC.
- Validate verified Publisher accounts at least once per twenty four hour period by checking that each verified publisher’s social media verification messages are still online.
- Contribute to available storage and bandwidth by running a protocol supported version of pinbotwizard Platform File Storage Manager, software that manages storage of the files published to the Open Index.
- Pinbotwizard maintains a minimum threshold of pins to ensure content persistence, current minimum is 5. Pinbotwizard tracks the pin count of each file and only pins files which are under the minimum threshold of pins.
- Pinbotwizard nodes pin only unpopular files; pinning of popular files is incentivized by "Pin to play" Pin to Play.
- Pinbotwizard development roadmap: When OIPWG quarterly platform reporting is implemented (see point 4 below), further logic will be added to dynamically adjust each platform file pinning requirement proportional to the platform’s revenue.
- Provide reporting for DMCA takedown requests, comply with fair use precedent and review/address takedown requests for any content published to the Open Index.
- Platforms must subscribe to the blacklist filters maintained by OIPWG. Blacklist offenses include: distributing content without consent from the rights holder (includes pirated commercial content), distributing content that has been "de-activated" by the Publisher, and universally abhorrent content (read more).
- Platforms who do not make a good faith attempt to address DMCA takedown requests within a reasonable time period as determined by OIPWG will be added to a blacklist and OIP revenue will be terminated.
- Platforms may appeal a takedown request to the OIPWG.
- DMCA takedown request process disincentives sybil attack efficacy. Content in question remains accessible in the Open Index and is not blacklisted until it has been reviewed.
- OIPWG is not involved in DMCA takedown requests for content that is not published to OIP, including platforms that display a combination of OIP content and other content.
- Report standardized commercial activity analytics once per quarter to the Open Index Protocol Working Group.
- Current planned content of the report includes: Timestamped record of each commercial transaction facilitated by the platform including the transaction ID(s), record ID, type of commercial activity (play, buy), total discounts applied by platform, pin count, and all demographic information the end user opts to share publicly.
A influencer shares links to content published in the Open Index and is paid a percent (determined by Publishers) of the payment activity driven by these links. Influencers are financially incentivized to share both commercial and non-commercial (tip-only) content. Similar to the Amazon Affiliates program.
Examples: social media influencers, bloggers, traditional advertisers
An influencer is valid when all of the following conditions are met:
- Send a influencer registration message with a publicly visible payment address to the Open Index, default payment address is currently planned to be BTC.
- Must use valid OIP links, if an influencer account is posting malformed, spoofing or malicious links the influencer account is added to the OIPWG blacklist.
Influencer account types:
- Verified Account: Connected to one or more social media accounts. A verified influencer account is verified by posting the hash of the influencer’s registration message on a publicly visible social media feed. A verified publisher account can share a regular OIP link and receive their percentage of any payment activity driven by this link.
- Non-Verified Account: Not connected to a social media account. A non-verified influencer must generate a unique link for every piece of content shared in order to receive payment.
Florincoin Blockchain Proof-of-Work Miners maintain the security of the Open Index and create the supply of tokens that are sold to publishers to be used for the publishing fees. Since getting Florincoin tokens from an exchange only indirectly incentivizes its mining, OIP defines a method, called Autominer, for miners to automatically set a sustainable Offer Price for their mined tokens which creates an incentive to mine, hold, and trade to the users who directly need it. As a result of this, Publisher demand directly drives the security of the Open Index. The services that ensure persistent file storage/bandwidth and secure publishing of new content to the Open Index are governed by the OIP specification, allowing permissionless participation in offering these services and making their work product function as fungible commodities; in other words, the protocol sees any 1MB of file storage as equivalent to any other 1MB, and any 1GH/s of POW as equivalent to any other 1GH/s of POW.
- Users who wish to participate in the Autominer system can either do so with their own sCrypt mining hardware, or more commonly, can do so by renting hardware from others on a periodic basis. The Autominer Application can be used to handle automatic renting of mining hardware based on market conditions and user preferences.
- Whether they wish to use their own hardware or rent from others, to participate in the system the user must register in the Open Index, and they must use a properly registered Autominer Pool.
- Whenever their Autominer Pool wins a block, it will look up various external points of data, called Historian Data Points, and stores them into the transaction comment of that particular block reward (coinbase).
- Based upon two important market factors, 1) the pools share of the overall mining activity and 2) the current cost to mine a token vs the current market exchange value, a reasonable margin is determined by a function called the Cross Chain Price Manager calculates the Offer Price for that particular block.
- Offers stay open until a Publisher closes them by executing a trade at the pre-determined Offer Price on a first-come, first-served basis.
- As a result, some offers will be open for a few hours, some could be open for a few weeks, but trades will always be made at a price that at least covers the miners costs, and in most conditions, allows a sustainable margin to encourage them to continue mining.
- OIPWG will maintain an open source reference client application for facilitating these trades, currently called TradeBot.
Autominer Pools encode Historian Datapoints into the transaction comment of the reward (coinbase) whenever they win a block. Historian data is used to determine the price of a block using the factors of (1) the actual cost to mine, (2) the market spot price, (3) the winning pool’s target margin and (4) the winning pool’s influence over the florincoin network.
Autominer manages miner participation in index security and file storage/distribution based on the miner’s unique preferences. It allows miners to "set it and forget it," and ensures they earn the minimum margin set in their preferences.
An autominer pool is any mining pool that properly encodes historian blockchain data into winning blocks.
An autominer pool is valid when all of the following conditions are met:
- Send a pool registration message to the Open Index with the URL of the service and the pool target margin.
- To update or change the pool URL or target margin, an update message is sent to the Open Index to modify the initial registration data.
Collaborative Defense is an optional process in autominer; it is an automated process that facilitates security of the network without reducing the users profits. *the set of market conditions & collaborative defense process needs to be defined
Tradebot is an application layer function, built into the UI anywhere that a user will be in need of protocol tokens (Florincoin & Filecoin). Most commonly used in the publishing process when a publisher needs to trade $USD -> BTC -> Florincoin to pay their publish fee. In order to prevent bad actors from abusing the process to sell their market-purchased tokens at a price higher than the market is pricing them, its limited only to the trade of tokens mined by protocol compliant autominer pools, with correctly encoded historian messages the coinbase of the tokens.
Cross Chain Price Manager
The protocol calculates an offer price for tokens that qualify as mined using the information captured by historian and the target margin set by their autominer pool, using the following formulae in order to account for both, the current mining conditions and the current market conditions:
Looked Up Variables:
Alexandria's hosted endpoint, the json value's key is networkhashpsfloNetHashrate, Florincoin network hashrate. In hashes per second. (fbdNetworkhashps) Can be looked up at
this hosted endpoint, the json value's key is pools:florincoin:hashrateautominerPoolHashrate, The given Autominer-Pool's hash rate. In hashes per second. Alexandria's instance can be looked up at
miningRigRentalsLast24hr, MiningRigRentals.com's 24 hour average cost per hash per second, per second of rental, in BTC. Looked up at the miningrigrentals API endpoint for sCrypt rentals, delivered as the 24 hour average cost to rent 24 hours of 1 megahash per second - this is divided by 86,400 (the number of seconds in 24 hours), and divided by 1,000,000 (to convert from megahashes to hashes) to become hashes per second per second.
Time since Autominer pool won its last block, in seconds.
Florincoin tokens won in block.
Alexandria's hosted endpoint, returned as the json field labeled weightedfloMarketPriceBTC, Exchange value per Florincoin token, in BTC. Can be looked up at
Alexandria's hosted endpoint, returned as the json field labeled USDfloMarketPriceUSD, Exchange value per Florincoin token, in US Dollars. Can be looked up at
poolWeightThreshold1, Protocol Governed Control Variable. Initial value is 0.3
poolWeightThreshold2, Protocol Governed Control Variable. Initial value is 0.45
Alexandria's hosted endpoint, returned as the json field labeled autominer-pool-data:alexandria-autominer-pool:TargetMargin Alexandria's autominer pool will initially use a value of 20Autominer-Pool's registered target margin. (Automner pool Target Margin) Can be looked up at
marketRatioThreshold1 Protocol Governed Control Variable. Initial value is 1.25
marketRatioThreshold2 Protocol Governed Control Variable. Initial value is 2
Protocol Governed Control Variable. (Exaggerator) Initial value is 2
Estimated cost of renting hashes to mine a Florincoin token. In BTC (costToMinePerToken)
AutoPool's Weight on the Florincoin network.
pool Weight multiplier.
Ratio between the resulting price with the full target margin and the current market price.
Market conditions multiplier
Offer Price. (in USD)
File Storage & Distribution
- File persistence is ensured because Platforms are required to store and seed a portion of the total size of all files in the Open Index. The amount of storage required of a Platform is commensurate with the percent of OIP market share captured by the Platform. Division of files for storage is random and not based on the content of the files. Example: Platform revenues are 30% of economic activity in OIP = Platform must store/seed 30% of total OIP files, by disk space.
- Playback performance is dependent on bandwidth. Similar to other p2p networks, bandwidth and file popularity are positively correlated; there is no upper limit on user file storage/distribution. Users are incentivized to store/distribute files via:
*Note: ipfs-cluster & filecoin are specifically related to IPFS. A publisher can use a different network for file storage/distribution because OIP uses interoperable transport layers, such as the Bittorrent Mainline DHT. Sia and Streamium also offer similar functionality. The OIPWG roadmap includes reference client software to implement the “pin to play” and “platform file storage manager” functions for additional networks like these.
- Alice and Bob: An explanation of the various kinds of users and service providers in the Open Index Protocol eco-system.
- Protocol Description: The features, design philosophy and economic principals behind Open Index Protocol.
- Message protocol: The JSON schema of various kinds of OIP messages and definitions of all terms used within them.
- Security Considerations: the questions, solutions & security considerations that have been analyzed.
- Back to the Main Page