Changes

From Ravencoin Wiki
Jump to navigationJump to search
459 bytes added ,  15:08, 3 January 2019
no edit summary
==Phase 5 - Messaging (Aim: Q1 2019)==
A message is "broadcast" if an owner token or channel token is sent in a transaction to the same address with the addition of an IPFS hash and an optional expiration date. The message isn't really broadcast in the sense of being transmitted to nodes, but rather each node will independently detect the special transaction type and display the message. Message display is subject to some heuristic anti-spam rules.
 
=== IPFS Integration ===
IPFS (Interplanetary File System) is used by Ravencoin for issuance meta-data, messaging, and transaction meta-data. Ravencoin must interact with IPFS in order to show messages because the message content is stored on IPFS. IPFS access should be on by default, but should be able to be turned off with a flag.
===Resources===
* [https://github.com/RavenProject/Ravencoin/tree/master/roadmap/messaging The Roadmap for messaging is here on Github]
* [https://github.com/RavenProject/Ravencoin/tree/master/roadmap/messaging-antispam The Roadmap for spam prevention is here on Github]
* [https://github.com/RavenProject/Ravencoin/tree/master/roadmap/ipfs The Roadmap for IPFS integration is here on Github]
===Use examples===

Navigation menu