7 Commits

Author	SHA1	Message	Date
JoelKatz	110a4a47f1	Use the transaction master.	2012-01-27 11:34:41 -08:00
JoelKatz	50e23112e3	Fix applying transactions with a local destination to the wallet.	2012-01-20 13:43:07 -08:00
JoelKatz	06d69888fd	Complete initial implementation of transaction relaying.	2012-01-19 15:56:06 -08:00
JoelKatz	94e4e1d04b	Handle all the weird edge cases, such as: ... A remote transaction is received *from* a local account. We neeed to update our balance and sequence tracking. A local transaction loses to a conflict.	2012-01-18 15:33:58 -08:00
JoelKatz	efb9fd7e1f	Extra debug	2012-01-18 14:14:46 -08:00
JoelKatz	56484476a9	More bugfixes.	2011-12-15 12:53:56 -08:00
JoelKatz	639ba9dfcb	NetworkOPs layer ... Begin coding the 'NetworkOPs' layer. This will provide most of the functions 'client' code will want to call such as functions to lookup transactions, check on their status, get balances, and so on. Much of the RPC layer will be a thin wrapper over these functions. The purpose of this layer is to permit the node to support these functions regardless of its operating mode or available data, as long as it's connected to the network. If synchronized and tracking the current ledger, it can do most functions locally. If not, it can ask for help from other nodes. If hopeless, it can return an error code.	2011-12-15 01:19:50 -08:00