It shows error when I open agama in native mode "Critical Error - Komodod is down"
what is wrong?
Topic: [ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B - page 320. (Read 1192000 times)
August 28, 2017, 03:11:09 PM
August 28, 2017, 02:48:11 PM
I was looking at the snapshot JL777 posted - http://5.9.253.204/snapshot.464000
Why are there so many addresses that have a balance of 3 coins?
Why are there so many addresses that have a balance of 3 coins?
August 28, 2017, 11:23:45 AM
What is there to market when it is still being developed, its a bad decision to market something when they can't specify any specific dates when the developments are coming out. It would only look that they are releasing a hype news.
I beg to differ.
Agama - the multicoin wallet app is at full product phase, just needing bug fixes and enhancements, which are always in progress
Jumblr - the KMD and soon to be BTC anonymizer is complete, just needs GUI
BarterDEX - a true decentralized exchange is also pretty much complete, GUI in progress
This is way more than any of the token ICOs out there has to offer. From what I can tell, most only has a whitepaper and look at how much marketing are involved in those projects.
If anything, KMD is a bit behind on the marketing department, but there has been talk in slack about this and I think the team agrees. It seems marketing will likely ramp up quite a bit over the next several weeks.
Edit: oh yeah, and let's not forget that Zcash, the crypto from which KMD forked barely has a GUI. They also just recently demonstrated a very basic atomic coin swap - something that Jl777 has had working and had been perfecting for over a year now.
I agree marketing is very importante nowadays. But marketing without product is something that mines credibility in the long run. Trash like Dash as the best marketing. When people realizes what it really is it can mine the credibility of a industry that is still seen as a whole. BTC and the other crypto are a block. People are not looking at it has the VERY diferente projects there are.
August 28, 2017, 11:10:56 AM
I am a Korean investor.
I think Komodo teams do not care too much about marketing.
Komodo teams have to do more aggressive marketing.
I think Komodo teams do not care too much about marketing.
Komodo teams have to do more aggressive marketing.
Last thing thats needed in crypto is marketing, komodo will do fine but marketing will come once everything is working, imho
August 28, 2017, 10:33:04 AM
BarterDEX will be the first true decentralized exchange with atomic swaps.It's a sleeping giant,be aware 
August 28, 2017, 10:14:36 AM
What is there to market when it is still being developed, its a bad decision to market something when they can't specify any specific dates when the developments are coming out. It would only look that they are releasing a hype news.
I beg to differ.
Agama - the multicoin wallet app is at full product phase, just needing bug fixes and enhancements, which are always in progress
Jumblr - the KMD and soon to be BTC anonymizer is complete, just needs GUI
BarterDEX - a true decentralized exchange is also pretty much complete, GUI in progress
This is way more than any of the token ICOs out there has to offer. From what I can tell, most only has a whitepaper and look at how much marketing are involved in those projects.
If anything, KMD is a bit behind on the marketing department, but there has been talk in slack about this and I think the team agrees. It seems marketing will likely ramp up quite a bit over the next several weeks.
Edit: oh yeah, and let's not forget that Zcash, the crypto from which KMD forked barely has a GUI. They also just recently demonstrated a very basic atomic coin swap - something that Jl777 has had working and had been perfecting for over a year now.
August 28, 2017, 10:13:55 AM
Hi, I am not able to see my balance in my wallet I only use basilisk mode. is there anything I can do?
too
Whats wrong? I have the AGAMA wallet and my Balance is also zero. Bug? Anything down? Try clearing cache and fetch wallet data.
You may have to click it a few times for it work (give it 5 mins between clicks)
You can check the address balance here:
https://www.kmd.host/
Thank you it worked, but only a short period of time. Now its zero balance again haha
August 28, 2017, 09:29:28 AM
I am a Korean investor.
I think Komodo teams do not care too much about marketing.
Komodo teams have to do more aggressive marketing.
I think Komodo teams do not care too much about marketing.
Komodo teams have to do more aggressive marketing.
What is there to market when it is still being developed, its a bad decision to market something when they can't specify any specific dates when the developments are coming out. It would only look that they are releasing a hype news.
August 28, 2017, 09:18:12 AM
Hi, I am not able to see my balance in my wallet I only use basilisk mode. is there anything I can do?
too
Whats wrong? I have the AGAMA wallet and my Balance is also zero. Bug? Anything down? Try clearing cache and fetch wallet data.
You may have to click it a few times for it work (give it 5 mins between clicks)
You can check the address balance here:
https://www.kmd.host/
August 28, 2017, 09:05:20 AM
Hi, I am not able to see my balance in my wallet I only use basilisk mode. is there anything I can do?
too
Whats wrong? I have the AGAMA wallet and my Balance is also zero. Bug? Anything down? August 28, 2017, 08:49:37 AM
I am a Korean investor.
I think Komodo teams do not care too much about marketing.
Komodo teams have to do more aggressive marketing.
I think Komodo teams do not care too much about marketing.
Komodo teams have to do more aggressive marketing.
Perhaps they are focusing on getting Barterdex, jumblr and all the other products working 100% and polished before worrying about building hype.
The way things should be done rather than all hype and nothing to back it up.
August 28, 2017, 08:43:02 AM
I am a Korean investor.
I think Komodo teams do not care too much about marketing.
Komodo teams have to do more aggressive marketing.
I think Komodo teams do not care too much about marketing.
Komodo teams have to do more aggressive marketing.
August 28, 2017, 07:46:08 AM
Hi, I am not able to see my balance in my wallet I only use basilisk mode. is there anything I can do?
August 28, 2017, 07:09:36 AM
There was no ICO for chips
There is no set aside for development
It is an ecosystem component and will act as a way to bring in many new markets into the komodo world as the LN and realtime gaming are not markets we were connected to in the past.
It is an old school PoW mining coin which was a pretty much direct fork of bitcoin 0.14
I didnt expect it to evolve into a 10+ peta hashrate so quickly.
"difficulty": 17000569.78940532,
I guess some people see promise in being able to play poker and other casino games for real money and then using JUMBLR. In order to maximize the privacy effect, JUMBLR is limited to KMD, so people will need to barterDEX into and out of KMD to be able to use JUMBLR.
There is no set aside for development
It is an ecosystem component and will act as a way to bring in many new markets into the komodo world as the LN and realtime gaming are not markets we were connected to in the past.
It is an old school PoW mining coin which was a pretty much direct fork of bitcoin 0.14
I didnt expect it to evolve into a 10+ peta hashrate so quickly.
"difficulty": 17000569.78940532,
I guess some people see promise in being able to play poker and other casino games for real money and then using JUMBLR. In order to maximize the privacy effect, JUMBLR is limited to KMD, so people will need to barterDEX into and out of KMD to be able to use JUMBLR.
August 28, 2017, 07:05:18 AM
Now that barterDEX is in a public beta and JUMBLR is active in the command line and there are many assetchains running, people can start to see the ecosystem coming into place.
normal bitcoin forks -> barterDEX -> KMD
KMD JUMBLR
barterDEX -> some coin
Using the above process, it is possible to convert any barterDEX supported coin into any other coin without any prior transaction history.
Combine that with the ability to do snapshots and dividend payments to any of the supported coins and it becomes possible to be sending revshares to totally private addresses (they are transparent but without any history!)
The CHIPS Lightning side of things is making progress, though I am having to wait for bugfixes from the blockstream guys. https://github.com/ElementsProject/lightning/issues
They have been very responsive to my bug feedback and I am pleasantly surprised at how seriously they take my issues I post. What most people dont realize is that without something like LN, segwit isnt much used at all and thus there is no BTC transaction capacity increase. All along I have been saying that segwit is not any scaling solution, but it does enable a lot of important new tech, like LN
For those that are expecting a slew of new LN tech right away, you will be disappointed. I am a decent C coder and it is not easy to use the LN as its model is quite different from anything previous. The closest analogue to it is the barterDEX, there is actually a fair amount of overlap at the high level due to the direct usage of utxo.
Anyway, the CHIPS is a new 10 second blocktime coin I created to experiment with Lightning tech. I also made a https://github.com/jl777/lightning fork that is customized for the CHIPS blockchain and already have a realtime privatebet test games able to be created. Still more work to do as far as generalizing the gameplay statemachines and properly tracking the LN bets, but pretty good progress in the short time it has been alive: https://bitcointalksearch.org/topic/annchips-kmd-platforms-ln-app-with-realtime-bettingdecentralized-shuffling-2078449
Also, the miners seem to be going a bit crazy as the network already has 5+ petahash
The exact role of CHIPS in the ecosystem is not yet determined, but since Lightning requires segwit and CHIPS is the only segwit coin in the komodo ecosystem, I expect that any usecase that requires realtime or micro payments would go through CHIPS. And yes, CHIPS already works with barterDEX, it worked the first try with just the right JSON config:
{\"coin\":\"CHIPS\", \"name\": \"chips\", \"rpcport\":57776,\"pubtype\":60, \"p2shtype\":85, \"wiftype\":188, \"txfee\":10000}
It really is that easy to add a new coin to barterDEX, at least at the low level technical connectivity. What is really required are nodes with active bids/asks for a coin and then it becomes much more useful
normal bitcoin forks -> barterDEX -> KMD
KMD JUMBLR
barterDEX -> some coin
Using the above process, it is possible to convert any barterDEX supported coin into any other coin without any prior transaction history.
Combine that with the ability to do snapshots and dividend payments to any of the supported coins and it becomes possible to be sending revshares to totally private addresses (they are transparent but without any history!)
The CHIPS Lightning side of things is making progress, though I am having to wait for bugfixes from the blockstream guys. https://github.com/ElementsProject/lightning/issues
They have been very responsive to my bug feedback and I am pleasantly surprised at how seriously they take my issues I post. What most people dont realize is that without something like LN, segwit isnt much used at all and thus there is no BTC transaction capacity increase. All along I have been saying that segwit is not any scaling solution, but it does enable a lot of important new tech, like LN
For those that are expecting a slew of new LN tech right away, you will be disappointed. I am a decent C coder and it is not easy to use the LN as its model is quite different from anything previous. The closest analogue to it is the barterDEX, there is actually a fair amount of overlap at the high level due to the direct usage of utxo.
Anyway, the CHIPS is a new 10 second blocktime coin I created to experiment with Lightning tech. I also made a https://github.com/jl777/lightning fork that is customized for the CHIPS blockchain and already have a realtime privatebet test games able to be created. Still more work to do as far as generalizing the gameplay statemachines and properly tracking the LN bets, but pretty good progress in the short time it has been alive: https://bitcointalksearch.org/topic/annchips-kmd-platforms-ln-app-with-realtime-bettingdecentralized-shuffling-2078449
Also, the miners seem to be going a bit crazy as the network already has 5+ petahash
The exact role of CHIPS in the ecosystem is not yet determined, but since Lightning requires segwit and CHIPS is the only segwit coin in the komodo ecosystem, I expect that any usecase that requires realtime or micro payments would go through CHIPS. And yes, CHIPS already works with barterDEX, it worked the first try with just the right JSON config:
{\"coin\":\"CHIPS\", \"name\": \"chips\", \"rpcport\":57776,\"pubtype\":60, \"p2shtype\":85, \"wiftype\":188, \"txfee\":10000}
It really is that easy to add a new coin to barterDEX, at least at the low level technical connectivity. What is really required are nodes with active bids/asks for a coin and then it becomes much more useful
August 28, 2017, 06:52:57 AM
Yesterday, a group of us tested out the jumblr process, the result can be seen on the blockchain.
The initial t->z transaction of course has the source address in it, but the second z->z transaction looks like:
https://kmd.explorer.supernet.org/tx/1097e598801cb0dfad8503e228f8a1c52c41f43e70b9e771f61c93f40e4e3dca
this transaction looks like:
Notice there are no normal vins or vouts, just some encrypted zeroknowledge proofs and ciphers
This is the true power of zcash tech and I believe with recent JUMBLR usage, the z->z transactions that KMD is doing is rivaling the number of those the zcash itself is doing. It is not easy to setup useful z->z transactions. I saw a website somewhere that showed zcash did several hundred z->z transactions last month. I believe we did more than that just yesterday.
At some point in the future, each of these z->z transactions will do a z->t and go into one of the jumblr_secret addresses that was specified by one of the JUMBLR participants. It is like the funds are teleported out of nowhere. There is no connection to any previous transaction.
Notice, it is not required for you to send funds to anybody else! It is single party tumbling and the anon set for this method is the total number of participants plus the z->z transactions running silent. That happens if you dont specify the jumblr_secret address, but make sure to have good backups of your wallet.dat!
The JUMBLR does not currently deal with IP correlation though, that is up to the user to make sure is private. But unless the attacker has IP router level logging, there is none of that information stored in the blockchain. The notary nodes are not used at all for JUMBLR, it is all inside komodod.
The more participants for JUMBLR, the better privacy for all.
The initial t->z transaction of course has the source address in it, but the second z->z transaction looks like:
https://kmd.explorer.supernet.org/tx/1097e598801cb0dfad8503e228f8a1c52c41f43e70b9e771f61c93f40e4e3dca
this transaction looks like:
Code:
./komodo-cli getrawtransaction 1097e598801cb0dfad8503e228f8a1c52c41f43e70b9e771f61c93f40e4e3dca 1
{
"txid": "1097e598801cb0dfad8503e228f8a1c52c41f43e70b9e771f61c93f40e4e3dca",
"version": 2,
"locktime": 0,
"vin": [
],
"vout": [
],
"vjoinsplit": [
{
"vpub_old": 0.00000000,
"vpub_new": 0.01000000,
"anchor": "ff297051027aa35735bcf93cebec44620f7f866c2da2d650870bfb1a8f1f8f1b",
"nullifiers": [
"cffa248e63fa8ee6a79395b8e985bb8ed4fd8b0eb8b73e6df7be457e13d28a33",
"b389d5153d5a1e09eecbee95b84eecfc8fcd96a90056ccc66df1d287b58b2fbf"
],
"commitments": [
"6cb90e6792772aeeca5c5a5cc0eda8812a378b02d39caffdc5965d5a863f4831",
"54f11b1b392620ba2a802349cf93825cf046336f53c067fbb990b7e319487328"
],
"onetimePubKey": "7c4af9fe45eaaced92b051b9340ab6aba351e041dcb0b3aeaba88707c4669574",
"randomSeed": "ead0df90ef6cc29a714341b363968f3820faf83df02d1d426df01b4c69c42158",
"macs": [
"a95c489182a11ae379765787d983d60ca1d52db6d1ac0ab1d002105fd0f2dce9",
"cd90ce44c315fec993330eec55c9c813c7daa6ed7374bf40a2855923eb1640c8"
],
"proof": "031ccb0f0b6e63265e8e18da38da7d208c23901c3379199e017f69cc12966d5539020dad9aa5115a67a9309e5870b7a7f0bf541b21ab113dc8352b626fedb91f8acb0b03a5cb80f07f15deadef4e78adda59131778b6ac331b4ff9277c2efc5faa00707526a9389c8d9483f8601d652d998616b02bf623abfc3144df35b8c15570725002125b741d725c33fd9626cc0934793a51e4091e4e50792b48ee9a9480a1f889570310f16b86c48c6eb96a942ae6e7e157448773e349cd301202795557516a85d135022e18c9788442e2ba6de76a2310fa07e4f5c645e426e933b033db506c39f96f1d021c4b5be292d3dc74685f80132c61e8545b2cdf049d2d14db2b0cad15fafbc1690310148296feff20daaf2324e2e346020b7648fec0577babff3c03d715567d47b4",
"ciphertexts": [
"1c8cd62e9918aec0ef3182859e8cac91e1a87143a3cd495e7cce350cbcc9404102f1eafbb38a33647a9ac62b54578a399b351c18159f9719fddca2a3dbe31fad71890058b8236dd18bbd7024d92b007fbfa7eebe9443eeff6549ff4b3c055bb9372de1ed7374dbb051e22536283dd649ee4c5bbe09863214091577b3054ffeaceb027509b7a502a14166d1b7e0090d899d7dd5f408ce16676eee580926621cad8bdf3a5c0e2b9507f906d916ca16ceeb931e88d20ffc0a240a0c3390211ab9330e64b1a8c3f48d6cb4fa240c00fa6f3727112f81491784c3bd9507648020298e224a67b437f28c1f6d67a4fa7b161a3e0aaf0dbbd7112abfde871740521f917d9150a5d27340c61ef9699c68934f4f9dc57b5f288f97883f0657b6680ae1d55cfc861e92764b72ec3a3789a78f120edb11a3bf0c91f12789efd21b8db79eead85271e0182a3fb036109ed0931fe537cdcd0f89feb76894a7d28934164519dfe7d664c0d93fdfcf928425b712f70529b883280bc6aad564714250558413b2449ba126f43b2a7d349565d8106ee11f401c7aadfd9fea9e5fc091a9feb0a574ef49315894b6dbf3be839f6e939c9768e1f5c0b5bf72b96543eb2fc488f40f61a249d609cee88b291570302497f2382d3f2d354672b733a316eb6dff043421a005c9e276e23a5cca6eaebf5ed7fc455679aab52c48f13ab1ccf1873196cc4428dfb03ad2c199b25de1f2be3d2ef1823031aea2f6000cafdda85ed251fdce5bccab64f73c3f2f254f4427199c52ef15787e984035ace0ea4bb6275cccb8aaab9e3d76f8ecd06757000d96aa7ec1391550a774a79e03bbc32fa78304",
"aaa8ee49dc1376edd21a5e029b294731f6869a7501e29fb67842dae184f243d9e9ba6750518a19f531c437fe9f896aed64be18620d668fbaa960e1437f22f97ad43a471cd61a5a3a16af51a3e81ae4f985ef25acf52f9b62db1d0b93afc56b144859bb1487fdb9fd9b7a1634c9294c03fd70277decd7406d23af5d0412d7c149d3e2e76953e8f6df02804da7217446eb702c991da7fca3bed3ae181851ee91e501420ec8383035275a8f19b6260c8470bc812798fb0c869a60b0e2dd56f4e97af54c64d76a1059f7a6590c0bccd8562015f65c8e73adcd471722cfcd2a09a6365cb45349ab68ae14b34384215c996d160b4b11f8333da77dd3b63ae91b5b5e5d27dfc271298e54078b801a64e5675b68c031a1a5255bba157734c208be82d24693cfa0f373aa8a3892f3d3e9ade15393ddba3f2f180f32c5a437181d6997f9abdea87a7b9a8b15809e13e176f89e6b584a6bde991241ba86da328b10c77b980665e4bec3e0ed330b66ffca707a1caa3628ca01bb3658299caa38b7db0be50b2d85fa325f016b3626f9be26b1799e6bd0c88f840bf37b91a9699cf06edb3c7de8011b5fb6edf3dd559070ad93d06b2cf1ed58e5805293cd202941fed1eed0c6835240ebc43e31550fb754910950d8940ec3d937b406cddfc83668c40c86e7d0a32a91e9a57f7c0ba70ee8f10ecefb7838d7705a6c224757bcdce7bed662fbc334d92f943f76a81fbeada24225d50a09b20836f15c519df4606cf711b3780047faeaff4617fd649bba342ada34169a9f571caac7048ebbdd9ba474e36c2db4f3c78be431d67c6fb13b7e60836e8bb3019bb42cd16395710d7428"
]
}
],
"blockhash": "0000000e52ea667d2d7684c6772430ee3538a2c500f647a378c63c38a95df366",
"confirmations": 12,
"time": 1503916446,
"blocktime": 1503916446
}
Notice there are no normal vins or vouts, just some encrypted zeroknowledge proofs and ciphers
This is the true power of zcash tech and I believe with recent JUMBLR usage, the z->z transactions that KMD is doing is rivaling the number of those the zcash itself is doing. It is not easy to setup useful z->z transactions. I saw a website somewhere that showed zcash did several hundred z->z transactions last month. I believe we did more than that just yesterday.
At some point in the future, each of these z->z transactions will do a z->t and go into one of the jumblr_secret addresses that was specified by one of the JUMBLR participants. It is like the funds are teleported out of nowhere. There is no connection to any previous transaction.
Notice, it is not required for you to send funds to anybody else! It is single party tumbling and the anon set for this method is the total number of participants plus the z->z transactions running silent. That happens if you dont specify the jumblr_secret address, but make sure to have good backups of your wallet.dat!
The JUMBLR does not currently deal with IP correlation though, that is up to the user to make sure is private. But unless the attacker has IP router level logging, there is none of that information stored in the blockchain. The notary nodes are not used at all for JUMBLR, it is all inside komodod.
The more participants for JUMBLR, the better privacy for all.
August 28, 2017, 06:46:02 AM
472000 Block is near and price is also rising KMD will become star of the crypto currency 
August 28, 2017, 06:13:59 AM
I also created a "secretaddresses" api call that generates a large set of derived addresses from a passphrase.
The following are the current API calls available from the barterDEX cli:
available localhost RPC commands:\n \
pricearray(base, rel, firsttime=0, lasttime=-1, timescale=60) -> [timestamp, avebid, aveask, highbid, lowask]\n\
setprice(base, rel, price)\n\
autoprice(base, rel, price, margin, type)\n\
goal(coin=*, val=)\n\
myprice(base, rel)\n\
enable(coin)\n\
disable(coin)\n\
inventory(coin)\n\
bestfit(rel, relvolume)\n\
ordermatch(base, txfee=0, rel, desttxfee=0, price, relvolume=0, txid, vout, feetxid, feevout, duration=3600)\n\
trade(price, timeout=10, duration=3600,)\n\
autotrade(base, rel, price, relvolume, timeout=10, duration=3600)\n\
swapstatus()\n\
swapstatus(requestid, quoteid)\n\
public API:\n \
getcoins()\n\
getcoin(coin)\n\
portfolio()\n\
getpeers()\n\
getutxos()\n\
getutxos(coin, lastn)\n\
orderbook(base, rel, duration=3600)\n\
getprices(base, rel)\n\
sendmessage(base=coin, rel="", pubkey=zero,)\n\
getmessages(firsti=0, num=100)\n\
clearmessages(firsti=0, num=100)\n\
secretaddresses(passphrase, num=10, pubtype=60, taddr=0)\n\
snapshot(coin, height)\n\
snapshot_balance(coin, height, addresses[])\n\
dividends(coin, height,)\n\
The following are the current API calls available from the barterDEX cli:
available localhost RPC commands:\n \
pricearray(base, rel, firsttime=0, lasttime=-1, timescale=60) -> [timestamp, avebid, aveask, highbid, lowask]\n\
setprice(base, rel, price)\n\
autoprice(base, rel, price, margin, type)\n\
goal(coin=*, val=
myprice(base, rel)\n\
enable(coin)\n\
disable(coin)\n\
inventory(coin)\n\
bestfit(rel, relvolume)\n\
ordermatch(base, txfee=0, rel, desttxfee=0, price, relvolume=0, txid, vout, feetxid, feevout, duration=3600)\n\
trade(price, timeout=10, duration=3600,
autotrade(base, rel, price, relvolume, timeout=10, duration=3600)\n\
swapstatus()\n\
swapstatus(requestid, quoteid)\n\
public API:\n \
getcoins()\n\
getcoin(coin)\n\
portfolio()\n\
getpeers()\n\
getutxos()\n\
getutxos(coin, lastn)\n\
orderbook(base, rel, duration=3600)\n\
getprices(base, rel)\n\
sendmessage(base=coin, rel="", pubkey=zero,
getmessages(firsti=0, num=100)\n\
clearmessages(firsti=0, num=100)\n\
secretaddresses(passphrase, num=10, pubtype=60, taddr=0)\n\
snapshot(coin, height)\n\
snapshot_balance(coin, height, addresses[])\n\
dividends(coin, height,
August 28, 2017, 06:06:29 AM
In preparation for the JUMBLR sharedrop, I decided to automate most of the process. So I wrote a few new api calls: "snapshot", "dividends" and now just added "snapshot_balance"
it is not designed to be fast and does not save/restore state (though this could be done by somebody else if they want to make a pull request). It just iterates through all the specified blocks and updates the balance of all the addresses.
That is how the files like http://5.9.253.204/snapshot.467000 are made, I just put the snapshot call in a primitive bash loop:
source userpass
ht=$1
while true
do
curl --url "http://127.0.0.1:7779" --data "{\"userpass\":\"$userpass\",\"method\":\"snapshot\",\"coin\":\"KMD\",\"height\":$ht}" > /var/www/html/snapshot.$ht
ht=$(( $ht + 100 ))
echo next hight $ht
sleep 6000
done
Now the snapshot API will work with any barterDEX supported coin and the list is sorted so it is essentially a richlist with all known addresses.
The "dividends" api allocates a specified dividend to all addresses not in the exclusion list and then auto generates shell script lines that can be "./komodo-cli sendtoaddress", which means all I have to do is cut and paste to do the actual sharedrop.
The third one is snapshot_balance, which does a snapshot and then scans it for the specified list of addresses and adds up the balance of those addresses. This way, you can put all the active addresses you have in the array and get an updated total from the snapshot.
Now we are all setup to do dividends for all the revshare assetchains and at the least we can run snapshot_loop to get a recent balance for all addresses
it is not designed to be fast and does not save/restore state (though this could be done by somebody else if they want to make a pull request). It just iterates through all the specified blocks and updates the balance of all the addresses.
That is how the files like http://5.9.253.204/snapshot.467000 are made, I just put the snapshot call in a primitive bash loop:
source userpass
ht=$1
while true
do
curl --url "http://127.0.0.1:7779" --data "{\"userpass\":\"$userpass\",\"method\":\"snapshot\",\"coin\":\"KMD\",\"height\":$ht}" > /var/www/html/snapshot.$ht
ht=$(( $ht + 100 ))
echo next hight $ht
sleep 6000
done
Now the snapshot API will work with any barterDEX supported coin and the list is sorted so it is essentially a richlist with all known addresses.
The "dividends" api allocates a specified dividend to all addresses not in the exclusion list and then auto generates shell script lines that can be "./komodo-cli sendtoaddress", which means all I have to do is cut and paste to do the actual sharedrop.
The third one is snapshot_balance, which does a snapshot and then scans it for the specified list of addresses and adds up the balance of those addresses. This way, you can put all the active addresses you have in the array and get an updated total from the snapshot.
Now we are all setup to do dividends for all the revshare assetchains and at the least we can run snapshot_loop to get a recent balance for all addresses
August 28, 2017, 05:33:01 AM
Im really so excited with this Jumblr snapshot . It goes to show you KMD is a crypto asset that cannot be ignored or taken for granted . This is the second time an asset will be redeemed at the expense of having a KMD in local wallet. I wonder if in the future there will be several more. Remember that once KMD completes its ecosystem , we will witness the real use of KMD as a fuel .
Jump to: