[{"data":1,"prerenderedAt":349},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fcore-tech\u002Fmain-wallet-entities-and-their-attributes":3,"docs-surround-\u002Fdocs\u002Fcore-tech\u002Fmain-wallet-entities-and-their-attributes":338},{"id":4,"title":5,"body":6,"description":327,"extension":330,"image":331,"meta":332,"navTitle":331,"navigation":333,"path":334,"seo":335,"stem":336,"__hash__":337},"docs\u002Fdocs\u002Fcore-tech\u002FMain-wallet-entities-and-their-attributes.md","User info",{"type":7,"value":8,"toc":326},"minimark",[9,13,26,30,41,45,75,79,230,234],[10,11,5],"h1",{"id":12},"user-info",[14,15,16,20,23],"ul",{},[17,18,19],"li",{},"Address (can be many): Unique ID money can be sent to\u002Ffrom. Each user\u002Fwallet can create and use any number of addresses. Address is assigned to one or more address categories (each category is denoted by name and color).",[17,21,22],{},"Name: Meaningful name is kept for semantic identification only (in a separate Directory service, should not be unique).",[17,24,25],{},"Avatar: Small and nice picture for the further identification.",[10,27,29],{"id":28},"address","Address",[14,31,32,35,38],{},[17,33,34],{},"a list of categories it is assigned to",[17,36,37],{},"a textual description (optional)",[17,39,40],{},"additional attributes such as: single use (won't be valid after the transaction is completed or failed) or time expiration (won't be valid once expired)",[10,42,44],{"id":43},"balance","Balance",[14,46,47,61],{},[17,48,49,50],{},"Amounts, aggregated by transaction states:\n",[14,51,52,55,58],{},[17,53,54],{},"Available: always shown, with LARGE font",[17,56,57],{},"In progress: Sending, Receiving, Change etc: shown when applicable (Alexandra Shelenkova do we need it?)",[17,59,60],{},"Locked: shown separately when applicable (sub-cases: \"maturing\" etc)",[17,62,63,64],{},"currency is:\n",[14,65,66,69,72],{},[17,67,68],{},"BEAM",[17,70,71],{},"GROTH (1*10^-8 of BEAM)",[17,73,74],{},"Consider estimated amount in BTC\u002FETH later on",[10,76,78],{"id":77},"utxo-details","UTXO details",[14,80,81,84,87,98,123,201,215,227],{},[17,82,83],{},"ID",[17,85,86],{},"Amount",[17,88,89,90],{},"Transactions it had participated in\n",[14,91,92,95],{},[17,93,94],{},"As output UTXO for incoming transaction, \"earned\" time is specified",[17,96,97],{},"As input UTXO for outgoing transaction, \"spent\" time is specified",[17,99,100,101],{},"Coin type\n",[14,102,103,114,117,120],{},[17,104,105,106],{},"Regular: just a regular coin, can receive most of the statuses (see below)\n",[14,107,108,111],{},[17,109,110],{},"Regular (received): received upon a successful completion of an incoming transaction",[17,112,113],{},"Regular (change): received by the sender when his UTXO is split during a successfully accomplished outgoing transaction",[17,115,116],{},"Transaction fee: paid by the user, is always created with \"Maturing\" status",[17,118,119],{},"Coinbase: mined when miner closed the block, is always created with \"Maturing\" status",[17,121,122],{},"Treasury: generated for maintenance and development of the project",[17,124,125,126],{},"Status\n",[14,127,128,131,195,198],{},[17,129,130],{},"Available: not in the transaction, can be spent",[17,132,133,134],{},"In progress, can have the following sub-cases:\n",[14,135,136,155,176],{},[17,137,138,139],{},"Incoming (draft) or Incoming: the amount is locked because of the ongoing incoming transaction\n",[14,140,141],{},[17,142,143,144],{},"Example:\n",[14,145,146,149,152],{},[17,147,148],{},"Alice has single UTXO of 100 BEAM and wants to send it fully to Bob (zero transaction fee for clarity)",[17,150,151],{},"Bob sees 100 BEAM as \"Incoming (draft)\" before that UTXO was registered in the node\u002Fblockchain",[17,153,154],{},"Bob sees 100 BEAM as \"Incoming\" when that UTXO was recognized registered in the node\u002Fblockchain",[17,156,157,158],{},"Outgoing: the amount is locked because of the ongoing outgoing transaction, new UTXO will be generated as a change once the transaction will be competed\n",[14,159,160],{},[17,161,143,162],{},[14,163,164,167,170,173],{},[17,165,166],{},"Alice has single UTXO of 100 BEAM and wants to send 20 BEAM to Bob (zero transaction fee for clarity)",[17,168,169],{},"Alice sees 100 BEAM are \"outgoing (locked)\" at first",[17,171,172],{},"Alice sees 80 BEAM as \"incoming (change)\" and Bob sees 20 BEAM \"incoming\"",[17,174,175],{},"Alice sees 80 BEAM as \"Available\" and Bob sees 20 BEAM \"Available\"",[17,177,178,179],{},"Maturing\n",[14,180,181,188],{},[17,182,183,184],{},"Reserved till ",[185,186,187],"time",{},": the amount will become available after the \"locked\" timeout will expire",[17,189,190,191],{},"Mined till block height ",[192,193,194],"height",{}," (similar to \"Reserved\", but measured in block height): the mined amount becomes available to miners only after the block height will be reached",[17,196,197],{},"Spent: gone with the completed outgoing transaction",[17,199,200],{},"Unavailable: for UTXO that cannot be spent anymore (due to transaction rollback or mining result rollback, the reason should be supplied just like for the \"Locked\" status)",[17,202,203,204],{},"Incoming Transaction details (if available, for example is not mined locally)\n",[14,205,206,209,212],{},[17,207,208],{},"Transaction ID - when clicked, should be taken to transaction list with the designated transaction details opened",[17,210,211],{},"Transaction completion time (ie time when UTXO was received)",[17,213,214],{},"Transaction Address ID (and its address group name and category if available)",[17,216,217,218],{},"Outgoing Transaction details (if available, for example not spent yet)\n",[14,219,220,222,225],{},[17,221,208],{},[17,223,224],{},"Transaction completion time (ie time when UTXO was spent)",[17,226,214],{},[17,228,229],{},"A history of status changes with its respective timestamps etc",[10,231,233],{"id":232},"transaction-details","Transaction details",[14,235,236,239,265,297],{},[17,237,238],{},"amount: shown as \u003Ccurrency + amount + state>",[17,240,241,242],{},"short state (displayed in transaction status in mobile)\n",[14,243,244,247,250,253,256,259,262],{},[17,245,246],{},"sending\u002Freceiving for Send\u002FReceive",[17,248,249],{},"in progress for Atomic Swap",[17,251,252],{},"sent\u002Freceived for Send\u002FReceive",[17,254,255],{},"completed for Atomic Swap",[17,257,258],{},"cancelled for both",[17,260,261],{},"failed for both",[17,263,264],{},"expired for both",[17,266,267,268],{},"detailed state (displayed on desktop or in transaction details in mobile)\n",[14,269,270,273,276,279,282,285,288,291,294],{},[17,271,272],{},"\"Waiting for network sync to complete\" - to indicate that transaction can't be started before the network sync is accomplished",[17,274,275],{},"\"Waiting for Sender\u002FWaiting for Receiver\" - to indicate that sender or receiver should come online to initiate the transaction",[17,277,278],{},"\"Handshaking\" - two wallets are negotiating the transaction details",[17,280,281],{},"\"Syncing with blockchain\" - the transaction is being registered with the node",[17,283,284],{},"\"Sending\u002FReceiving\" - the transaction is taken care by the blockchain, some miner needs to PoW and to add it to a block, the block should be added to the blockchain",[17,286,287],{},"\"Sent\u002FReceived\" - the transaction is completed",[17,289,290],{},"\"Cancelled\" (by Sender, due to Rollback)",[17,292,293],{},"\"Expired\" (by timeout)",[17,295,296],{},"\"Failed\" (should come with the user-friendly actionable reason\u002Fdescription)",[17,298,299,300],{},"time for every status change in the transaction lifecycle such as:\n",[14,301,302,305,308,311,314,317,320,323],{},[17,303,304],{},"creation timestamp",[17,306,307],{},"peer online timestamp",[17,309,310],{},"peer offline timestamp",[17,312,313],{},"timestamp for each confirmation",[17,315,316],{},"deletion time (where appropriate)",[17,318,319],{},"peer addresses (sending, receiving escrow in the future etc), each address can be assigned to an address groups",[17,321,322],{},"related UTXOs (ie IDs of transactions, outputs of which serve as inputs for the current transaction)",[17,324,325],{},"textual annotation (optional), sender and receiver have separate annotations, each is stored locally",{"title":327,"searchDepth":328,"depth":328,"links":329},"",2,[],"md",null,{},true,"\u002Fdocs\u002Fcore-tech\u002Fmain-wallet-entities-and-their-attributes",{"title":5,"description":327},"docs\u002Fcore-tech\u002FMain-wallet-entities-and-their-attributes","0ku5tuzkdNvjwOBM-lZENphsst1yFdPleYsN33BBcAY",[339,344],{"title":340,"path":341,"stem":342,"description":343,"children":-1},"MW CLA","\u002Fdocs\u002Fcore-tech\u002Fmw-cla","docs\u002Fcore-tech\u002FMW-CLA","MW-CLA stands for Mimblewimble Confidential Lelantus Assets",{"title":345,"path":346,"stem":347,"description":348,"children":-1},"Merkle Trees","\u002Fdocs\u002Fcore-tech\u002Fmerkle-trees","docs\u002Fcore-tech\u002FMerkle-trees","BEAM uses various kinds of Merkle trees and proofs.",1783006076491]