Development

From Ravencoin Wiki
Jump to navigationJump to search


This section of the wiki aims to help document the development work done related to the Ravencoin network.

Future dev chats will be available on discord - #irc-ravencoin-dev

Historic dev chats on IRC, now moved to Discord.

Open weekly or fortnightly dev chat on IRC check https://www.ravencointalk.org/post/ravencoin-open-developer-meeting-9816968?pid=1305079154

IRC: https://webchat.freenode.net/?channels=ravencoin-dev

Archive of the conversation on the 10th Aug 2018 on Reddit https://www.reddit.com/r/Ravencoin/comments/96at36/irc_log_from_ravencoin_open_developer_meeting_aug/


Ravencoin platform development

Currently organized and based on Tron his talk at the Ravencoin NH meetup (October 11, 2018): [1]

Phase 1 - Ravencoin launch & mining algorithm

In addition to the X16R algorithm, most of the core code changes are in the chainparams file.

The details are broken down on the wiki page: Chainparams.

If you are looking to port existing Bitcoin applications to include Ravencoin - there are some useful parameters available from work done in the Ledger integration code on GitHub.

Summarized on the wiki page: Ledger integration

If you are looking for typical parameters needed for wallet integration - there is a summary on the Wallet integration page.

It's worth mentioning, whilst we all try to keep these pages up to date, the RavenProject code on GitHub could change and these pages could become out of sync. Please validate on https://github.com/RavenProject/Ravencoin.

Phase 2&4 - Assets, Subassets & Unique assets

Asset testnet live. Check testnet for more details, and Testnet-technical for details about the anatomy of a Ravencoin asset transaction script.

Asset FAQ written by Tron on Medium https://medium.com/@tronblack/ravencoin-asset-faq-e0d04d460e9b

(20 Aug 2018) In addition to asset functionality being on available to test on testnet - Ravencoin is forking to include Dark Gravity Wave to protect itself against hash rate attacks - exchanges and mining pools need to upgrade as soon as possible to the latest wallet release, users as soon as they want to use their coins. Forks_and_updates

Assets (cost 500 RVN):

  • Token name - Must be unique
  • Number of tokens - From 1 to 21 billion
  • How divisible? - From not divisible to 8 decimal places (0.00000001)
  • Reissuable (yes/no)
  • Include meta-data (agreement, company, contact, etc)

Subassets (cost 100 RVN):

  • Token name - Must be unique when combined with token
  • Number of tokens - From 1 to 21 billion
  • How divisible? - From not divisible to 8 decimal places (0.00000001)
  • Reissuable (yes/no)

Unique Assets (cost 5 RVN) - create one-of-a-kind assets:

  • ART#VenusDeMilo
  • CAR#<VIN number>
  • COOLGAME#SwordOfThor

Phase 3 - Dividends/Rewards

Pay your token holders in RVN. Turn your profits into RVN and send out to all holders of your token by percentage held.

Dividend support can be done without modifying the protocol. We can add it to a version of the software that can be used by the payer, without requiring others to upgrade (i.e., a soft fork).

If you require this functionality ask in #dev channel on discord as there is a python script to get owners of assets, and someone could write code to loop through owners paying to their address.

Phase 5 - Messaging

Broadcast a message to all of your token holders.

  • Send information about your token.
  • Send alerts relevant to your project.
  • Send information about a shareholder vote.
  • Use Raven messaging for other systems.

Phase 6 - Voting

Issue a special vote token to every holder of your token.

  • Send to <address X> to vote for X proposal
  • Send to <address Y> to vote for Y proposal

Second tier web voting can be built on top of this protocol.

Phase 7 - Compatible Mode

Allows newly created assets to appear exactly like RVN, LTC, or Bitcoin for easy integration into exchanges, wallets, explorers, etc. This speeds adoption into the larger crypto ecosystem.

Using the Ravencoin platform

Asset control

issue (asset_name, qty, to_address, change_address, units, reissuable, has_ipfs, ipfs_hash)

Issue an asset with unique name. Unit as 1 for whole units, or 0.00000001 for satoshi-like units. Qty should be whole number. Reissuable is true/false for whether additional units can be issued by the original issuer. 

issueunique (root_name, asset_tags, ipfs_hash, to_address, change_address)

Creates a unique asset from a pool of assets with a specific name. Example: If the asset name is SOFTLICENSE, then this could make unique assets like SOFTLICENSE:38293 and SOFTLICENSE:48382 This would be called once per unique asset needed. 

reissue (reissue asset_name, qty, to_address, change_address, reissuable, new_unit, new_ipfs )

Issue more of a specific asset. This is only allowed by the original issuer of the asset and if the reissuable flag was set to true at the time of original issuance. 

transfer (asset_name, qty, to_address)

This sends assets from one asset holder to another. 

listassets (assets, verbose, count, start)

This lists assets that have already been created. 

listmyassets ( asset, verbose, count, start )

Lists your assets. 

listassetbalancesbyaddress (address)

Lists asset balance by address. 

listaddressesbyasset (asset_name)

Lists addresses by asset. 

getassetdata (asset_name)

Lists asset data of an asset.

Other documentation

Atomic swaps: https://github.com/RavenProject/Ravencoin/blob/master/doc/atomicswaps.md

Community Projects

Brianmct RavenNodes - forked from Bitnodes - project to show all the active Ravencoin nodes

RavencoinRPC-PHP - PHP RPC API for communicating with the Ravencoin Network.

Underdarkskies - various projects including an extended RPC version of Ravencoin.

Retrieved from ‘https://raven.wiki/index.php?title=Development&oldid=1415’