iguanacore is in testing now, I am seeing around a one hour time to sync on home connection of 20mbps, less than half hour on much faster connection.
it creates historical read only files via parallel sync as described at
https://bitco.in/forum/forums/iguana.23/yes, iguana has a child board on the bitco.in forum. I asked for one here, but was ignored for some reason. The following are some relevant threads on this forum.
https://bitcointalk.org/index.php?topic=1377459.0https://bitcointalk.org/index.php?topic=1394020.msg14159884#msg14159884https://bitcointalk.org/index.php?topic=1399028.0https://bitcointalk.org/index.php?topic=1387119.0next step is to validate data and low level RPC calls like listunspent, but iguanacore supports block explorer level API, so really it needs to be tested against insight explorer, but even that doesnt have a way to check balances as of a specific height. iguanacore supports that
I am testing in native mode on osx and unix, but it should still work as chrome app and I saw the build guys got things working for windows, but not sure what its exact status is as I dont run windows.
All the above is well known stuff in slack, but it seems there is market price activity recently and I wanted to make sure people who are not on slack are up to date and can make their own decisions.
If anybody is up for testing the timing of full sync that would be great.
https://github.com/jl777/SuperNET is the repo and it even has a readme with instructions.
after it is built and you run it, just browse to
http://127.0.0.1:7778that will show a zillion API calls in a test page but there is also a link to the port7777 GUI in the upper left. From there you should be able to activate sync.
or you could just run ../agents/iguana in one console and from another:
curl --url "
http://127.0.0.1:7778" --data "{\"agent\":\"iguana\",\"method\":\"addcoin\",\"newcoin\":\"BTCD\"}"
curl --url "
http://127.0.0.1:7778" --data "{\"agent\":\"iguana\",\"method\":\"addcoin\",\"newcoin\":\"BTC\"}"
the above will get both coins going, so better to just start with one and make sure things are working. for now, it is not tested against large number of system configs, so cant guarantee it is perfect in all cases. let me know of any issues
James
P.S. GUI is in parallel development, following is current status for them:
Completed on wallet
1. working wallet send
2. showing balance (updated after every minute)
3. showing all the addresses of account in wallet information
4. selection of coin at login (for v0.01 depends on username & passoword)
5. checking the correctness of passphrase using passphrasechange rpc
6. checking for possible coin port at login (for both BTCD and BTC)
Remaining on wallet
1. showing Login error
2. Showing updater (or spinner ) when sending/updating and stopping other task while spinning
3. add implementation of addmultisigaddress
4. use send from only when selected from wallet information
5. Show balance on main activity tab
6. add pagination of transactions
7. change account name for an address using setaccount
8. show transaction details using blockexplorer button (internally by rpc in v0.1)
9. connection login and select coin option
10. clean old code
###
completed on Instantdex
1. Completed transaction on 1by1 view (buy/sell)
2. implemented aveprice and used tag as botid and called resume method in combined view
3. given option to select between the
remaining
1. complete combined view
2. withdraw api implementation (shows permission error)
3. other enhancements on GUI
###
port7777 ugly GUI is functional and able to issue quite a few API calls
port7778 API test page is working
docs.supernet.org has API bindings