Difference between revisions of "Bailment Database"
Jump to navigation
Jump to search
(Initial page creation) |
m (Update links and correct category, improve justification) |
||
| Line 1: | Line 1: | ||
==Purpose== | ==Purpose== | ||
| − | The [[audit server]] and [[transaction server]] both store a deposit database which permanently associate deposit addresses with [[nym|nyms]]. This allows unsolicited or duplicate deposits to be properly credited. | + | The [[Audit Server (voting pools)|audit server]] and [[Transaction Server (voting pools)|transaction server]] both store a deposit database which permanently associate deposit addresses with [[nym|nyms]]. This allows unsolicited or duplicate deposits to be properly credited, and also prevents a malicious transaction server for assigning a deposit address to two different nyms. |
==Format== | ==Format== | ||
| Line 8: | Line 8: | ||
| − | [[address identifier]] | + | [[Wallet_(blockchain)#Address_Identification|address identifier]] |
pendingBailment ID, | pendingBailment ID, | ||
| Line 15: | Line 15: | ||
| − | [[Category:Voting Pool | + | [[Category:Voting Pool Technical Specifications]] |
Revision as of 07:59, 26 May 2014
Purpose
The audit server and transaction server both store a deposit database which permanently associate deposit addresses with nyms. This allows unsolicited or duplicate deposits to be properly credited, and also prevents a malicious transaction server for assigning a deposit address to two different nyms.
Format
The database contains the following fields:
pendingBailment ID,
nym
