Tree: e3d14c573b

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 'e3d14c573b'

${ noResults }

Commit Graph

431 Commits (e3d14c573b6a8f827c4e9592312690fb7c88ca79)

Author	SHA1	Message	Date
jl777	e10660377c	test	8 years ago
jl777	e1931425b8	test	8 years ago
jl777	6e7e5c2df7	test	8 years ago
jl777	1f009f4c9d	test	8 years ago
jl777	1703a9132c	basilisk getinfo	8 years ago
jl777	7f9d9d7160	test	8 years ago
jl777	2228fdba38	test	8 years ago
jl777	b0136f16b8	fix remove file and move file for windows	8 years ago
jl777	82fa535737	fix renaming files in windows to rename instead of delete! The port of rename file was deleting files, which kind of makes creating a bundle difficult! I wrote a mini-test suite to test most of the system specific functions, this can be invoked via command line ../agents/iguana OStests or via compile time -D IGUANA_OSTESTS	8 years ago
jl777	ac47717bb4	test	8 years ago
jl777	5fc784db5c	test	8 years ago
jl777	458173a8a6	vs compat	8 years ago
jl777	7bee16ffa8	test	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	f15c6881af	fixed history	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	798d4ea881	test	8 years ago
jl777	e9fcba1c36	test	8 years ago
jl777	562386d2bf	test	8 years ago
jl777	361af6eec9	test	8 years ago
jl777	d3997bf561	test	8 years ago
jl777	3b3b6d9d30	test	8 years ago
jl777	c1e9bee4eb	test	8 years ago
jl777	3cc77768aa	test	8 years ago
jl777	549e5456b7	test	8 years ago
jl777	8c01f32876	test	8 years ago
jl777	361d5fb575	test	8 years ago
jl777	496f812832	active handle gets all coins	8 years ago
jl777	faed022e4e	test	8 years ago
jl777	73262cc1fd	test	8 years ago
jl777	a53570544c	test	8 years ago
jl777	62aadf9c03	test	8 years ago
jl777	f3236330bc	test	8 years ago
jl777	cd10f1a666	test	8 years ago
jl777	ab83f52641	test	8 years ago
jl777	4b8f4da10c	test	8 years ago
jl777	27fd324636	test	8 years ago
jl777	2f411f119f	test	8 years ago
jl777	a619097699	test	8 years ago
jl777	58ed09689b	test	8 years ago
jl777	ea4f44b73e	test	8 years ago
jl777	df96e66ac2	test	8 years ago
jl777	1acb69cb38	test	8 years ago