'Offline' Wallet

Target release	TBD
Epic
Document status	DRAFT
Document owner	@Medha Parlikar (Unlicensed)
Designer
Developers
QA

Goals

Growth

Background and strategic fit

A company may want to provide a wallet service without operating as an RChain node. This will allow transactions to take place across the RChain network (transactions in Rev) that take place without requiring that each wallet service become a node operator.

Assumptions

With CASPER, there is an assumption that one can identify the complete list of validators at any given time.

Requirements

	Title	User Story	Importance	Notes

	Title	User Story	Importance	Notes
1	Send transaction to nodes	As a wallet provider, I need to know who will validate my transactions.	Must Have	Define how a transaction is sent by an offline provider to the RChain network.
2	Validate that a transaction has been confirmed	As a wallet provider, I need to know when my transaction has made it on to the longest chain.	Must Have	Define how transactions are confirmed.
3	How many nodes are needed?	As a wallet provider, I need to know how many copies of the transaction I need to send out so that the transaction is reliably validated	Must Have	A wallet provider is going to want his transactions to be reliably verified within a certain time period, how many validators does the transaction need to be sent to in order to ensure a given validation time.

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome

Question	Outcome