Tree: c3589ac483

acspeed

beta

beta_season3

blackjok3r

dPoW

dPoW2

dev

etomic

fix-mm-build

fix-mnotary_arg

jl777

master

olddPoW

pass-iguana-arg

patch-1

patch-10

patch-11

patch-12

patch-13

patch-14

patch-2

patch-3

patch-4

patch-5

patch-6

patch-7

patch-8

patch-9

quote-mnotaryrun-args

release/v0.1

win-cross

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'c3589ac483'

${ noResults }

Commit Graph

101 Commits (c3589ac483194fb198d7fa38ccd39c2e2e1ec0e1)

Author	SHA1	Message	Date
jl777	aca83f21ec	voting server	8 years ago
jl777	57558541d5	improve RT	8 years ago
jl777	6622f13c2f	skip validation of join splits	8 years ago
jl777	78d40efae3	fix basilisk native coin port timeout	8 years ago
jl777	747ce715c1	test	8 years ago
jl777	3e5cf4abb5	remote listunspent	8 years ago
jl777	4aa13e7d60	basilisk sendtoaddress	8 years ago
jl777	8ddb3dca5a	test	8 years ago
jl777	f39b1242c3	test	8 years ago
jl777	b1fe7402eb	better exit handling	8 years ago
jl777	54056bc131	basilisk listunspent, balances, history	8 years ago
jl777	176b1bc512	debug prints	8 years ago
jl777	0de822d1ec	basilisk sendtoaddress	8 years ago
jl777	cf7728ccd9	test	8 years ago
jl777	6dc61e5656	test	8 years ago
jl777	e7db944b42	better exit handling	8 years ago
jl777	707987a0d0	basilisk listunspent, balances, history	8 years ago
jl777	e08c7e16ab	debug prints	8 years ago
jl777	e1931425b8	test	8 years ago
jl777	1f009f4c9d	test	8 years ago
jl777	1703a9132c	basilisk getinfo	8 years ago
jl777	25660ec88e	debug version	8 years ago
jl777	421314f16d	sendtoaddress fixed reworked internals for basilisk/history api by using iguana/balance api and sendtoaddress uses this data. tested finding and using utxo in completed bundles, and also in the RT bundle. Left to test are detecting a spend of RT bundle in the RT bundle. also amounts and txfees are a bit off, but basic sendtoaddress should work in all cases other than bugs left to do is to lock utxo after being used so multiple tx per block can be sent, otherwise the same utxo could be selected and that is invalid	8 years ago
jl777	ff090aaab1	fixes	8 years ago
jl777	cf67a62391	new history	8 years ago
jl777	e2e4caebd4	debugging	8 years ago
jl777	cc0a30764c	Revert "Revert "txdetails and helper functions, proposed fix for #59"" This reverts commit 02ae9881ae.	8 years ago
jl777	02ae9881ae	Revert "txdetails and helper functions, proposed fix for #59" This reverts commit d4f19ce7eb.	8 years ago
jl777	d4f19ce7eb	txdetails and helper functions, proposed fix for #59 https://github.com/jl777/SuperNET/issues/59 required retrieving additional details from transaction info RPC. both getrawtransaction and get transaction use the same code path and list transactions also uses the get transaction path, so all paths should now have the txdetails fields: "category": "receive", "amount": 0.50000000, "confirmations": 24466, "blockhash": "00000000000000000517ce625737579f91162c46ad9eaccad0f52ca13715b156", "blocktime": 1448045745, "blockindex": 78, "label": "", the block index and label fields are currently not supported. Also since iguana has data for all addresses, not just wallet addresses and including ‘push’ addresses, the ‘category’ field has additional return possibilities: ‘isp2sh’ is returned for any ‘p2sh’ address, regardless of whether some or all of the required privkeys to spend the ‘p2sh’ address are in the wallet. to determine partial or full signature capability would require interpreting the script in place, and the returned information would need to indicate conditional states, i.e. cltv, multisig, if/else, etc. so this part is a won’t fix for non-p2sh addresses, if it is in the wallet it will return “receive” or “send” depending on whether the txid/vout outpoint has been spent or not. for addresses no in the wallet, it will return “unspent” or “spent”. Note that a locked wallet might or might not get as far as calling this txdetails, but if it did, it would return “unspent”/“spent” even for an address in the wallet as it has no way to know if it is indeed a wallet address	8 years ago
jl777	8595854a08	jsonQ separated into global and coin specific queues using a mutex to serialize all API requests causes unacceptable latency in some cases. Not serialized can lead to queries into a dataset with unstable state. To fix this, all JSON requests are split into coin specific queues whenever possible and the global queue is only used when the coin can’t be determined from the JSON request. Each coin’s main thread calls the iguana_jsonQ to process that coin’s queue of requests only after all the dataset updates are complete to assure only valid data is returned. Since any previous large latencies were when a specific coin was updating its dataset and the dataset can’t be safely accessed during that time, the delay in processing that coin’s request doesn’t create any additional latency this bug fix is in response to @pbca26 report of “iguana_pkhashbalance: unexpected non-ptr lastpt” which is an error that is most likely caused by accessing the dataset at the wrong time.	8 years ago
jl777	3cc77768aa	test	8 years ago
jl777	8c01f32876	test	8 years ago
jl777	496f812832	active handle gets all coins	8 years ago
jl777	faed022e4e	test	8 years ago
jl777	f3236330bc	test	8 years ago
jl777	cd10f1a666	test	8 years ago
jl777	27fd324636	test	8 years ago
jl777	df96e66ac2	test	8 years ago
jl777	1acb69cb38	test	8 years ago
jl777	ef0849efa5	test	8 years ago
jl777	01de4aacc8	test	8 years ago
jl777	b8735b216c	test	8 years ago
jl777	992db5b00a	test	8 years ago
jl777	29e33cefeb	test	8 years ago
jl777	2fe109193f	test	8 years ago
jl777	5ff24b6fd2	test	8 years ago
jl777	516cb8ee2d	test	8 years ago
jl777	2a1dd75416	test	8 years ago
jl777	dcc11b4048	test	8 years ago
jl777	05131e0966	test	8 years ago