Search content
Sort by
Showing 20 of 155 results by markasoftware
The Mithril that is starting to get on exchanges is not the same one as in this ANN. It is here: https://bitcointalk.org/index.php?topic=3108554.0
Re: How to browse the internet and run suspect software safely?
You may wish to look into https://qubes-os.org, it's designed to make it quite easy to isolate applications. So you can run untrusted software, and if it turns out to be a virus, oh well, the rest of your system is completely safe.
I think Ledger will not be supporting anything but BCH and BTG because BTG was already almost a scam and everything since then is even worse somehow. You don't necessarily need to keep your coins on an exchange though; you could just, after each fork, move all BTC to a new seed, then import the old seed into a program which lets you extract the private keys, then import those private keys into the full node software for the forked coin. However, this is really a pain, and I think all forks from here on out are going to be nearly worthless anyways.
Is there a fork or another program that can do work on more than one pubkey at the same time?
No, it is a technological limitation. Look at my post in this thread a few messages ago about a possible scheme for mining on multiple public keys (originally invented by ArcCsch). However, this would not be simple, it would require new pool software as well and is a pretty invasive change.
Is there a method of writing the -f document in vanitygen that will allow multiple split pair jobs at once?
The -P flag is where you place the pubkey for someone looking for a job done securely for them.
The -f flag allows a file with one job per line, but from what I can find it only allows direct searches, not split pair searches.
work.txt
Is there a way to place the public keys a document file?
pubwork.txt
The -P flag is where you place the pubkey for someone looking for a job done securely for them.
Code:
vanitygen -P 04ED64430556D8A00175291C1DE84D4989D5568AFA0DEB7F9331766AF077B01470E4A44C5D7347E64AA709E8A475D4AE7658E5C9DD96CF3C8061D430BBDE1C45D7 1machine
The -f flag allows a file with one job per line, but from what I can find it only allows direct searches, not split pair searches.
work.txt
Quote
1mean
1bean
1machine
1bean
1machine
Code:
vanitygen -f work.txt
Is there a way to place the public keys a document file?
pubwork.txt
Quote
04527435D4974ED77372A24BF082E12886521DA7E302E0F73DBF733099B5641A5F1838203A79C0B DC45270D29E9CE7F1316D51084320DBD3CE05B34C3C717B6F38,1mean
041171B44E4FF72800E479DB850F2CD51D84DB50445D03ADA894A787D054D2B8B67BBE01026B026 8AFED68682084E5B56B7891F0B5A650F663D3C635C0C580AD37,1bean
04ED64430556D8A00175291C1DE84D4989D5568AFA0DEB7F9331766AF077B01470E4A44C5D7347E 64AA709E8A475D4AE7658E5C9DD96CF3C8061D430BBDE1C45D7,1machine
041171B44E4FF72800E479DB850F2CD51D84DB50445D03ADA894A787D054D2B8B67BBE01026B026 8AFED68682084E5B56B7891F0B5A650F663D3C635C0C580AD37,1bean
04ED64430556D8A00175291C1DE84D4989D5568AFA0DEB7F9331766AF077B01470E4A44C5D7347E 64AA709E8A475D4AE7658E5C9DD96CF3C8061D430BBDE1C45D7,1machine
You can only mine with one public key at a time, so this doesn't make much sense. You can mine multiple addresses that all use the same public key, but not multiple addresses each with different pubkeys.
Woah, I swear I just thought of this same thing today! I think it is secure.
For the issue you mentioned, a possible solution: Require the private keys to be revealed and replaced at random intervals even if an address is not found. That way, it is impossible for somebody to maliciously withhold addresses, because they don't know if this time is "real" or not -- it may be the pool randomly asking to renew the private keys, or it may be that an address was found. An additional measure that could be taken is requiring people to put in payment before their address is mined, and if they withhold then you stop mining their address without refund, so they are incentivized to reveal their keys.
One big problem I see is how do you make it easy to handle private key revealing/generation? Most people don't have a personal server at home they can use. So, you can send an email whenever an action needs to be taken, then they can run the application to reveal and regen keys. But this requires them to frequently do it, which is a pain, and also means that whenever they don't do it their mining stops.
A partial solution is to generate many keypairs at once, and host many public keys on the pool servers. So, when an address is found, next round can begin immediately. Then, you only have to run the special application to give out the private keys once every few days. It just means that, if your address was generated, that you don't get access immediately. I think this is acceptable. EDIT: You could actually just use a deterministic HD wallet and give the xpub to the server to let it generate an arbitrary number of public keys.
Overall, it's a great idea, with tons of potential. When I'm done with my current project, I may begin work on a pool server and client application that creates and reveals keys. I think it can be backwards-compatible with oclvanityminer because all the miners actually need to do is mine againts an ECDSA public key, which is already what they do. If you are interested in building part of it, that would be great!
For the issue you mentioned, a possible solution: Require the private keys to be revealed and replaced at random intervals even if an address is not found. That way, it is impossible for somebody to maliciously withhold addresses, because they don't know if this time is "real" or not -- it may be the pool randomly asking to renew the private keys, or it may be that an address was found. An additional measure that could be taken is requiring people to put in payment before their address is mined, and if they withhold then you stop mining their address without refund, so they are incentivized to reveal their keys.
One big problem I see is how do you make it easy to handle private key revealing/generation? Most people don't have a personal server at home they can use. So, you can send an email whenever an action needs to be taken, then they can run the application to reveal and regen keys. But this requires them to frequently do it, which is a pain, and also means that whenever they don't do it their mining stops.
A partial solution is to generate many keypairs at once, and host many public keys on the pool servers. So, when an address is found, next round can begin immediately. Then, you only have to run the special application to give out the private keys once every few days. It just means that, if your address was generated, that you don't get access immediately. I think this is acceptable. EDIT: You could actually just use a deterministic HD wallet and give the xpub to the server to let it generate an arbitrary number of public keys.
Overall, it's a great idea, with tons of potential. When I'm done with my current project, I may begin work on a pool server and client application that creates and reveals keys. I think it can be backwards-compatible with oclvanityminer because all the miners actually need to do is mine againts an ECDSA public key, which is already what they do. If you are interested in building part of it, that would be great!
I've been thinking about this for a bit, and mainly about the possibility of merge-mining many addresses at once, to massively increase efficiency. This is what I've come up with:
1. Everybody who wants an address generates an ECDSA keypair, a Personal Pair
2. Everybody gives their public keys to the pool, which combines them into the Combined Public Key
3. The pool distributes the Combined Public Key to miners. The miners generate random keypairs until they find the right address when combined with the Combined Public Key, the same way it's done with split mining.
4. The randomly generated private key is given to the person who requested the address
5. Everybody but the person who requested the address gives their private key to the person who requested it.
6. The person who requested the key can spend funds by combining the pool's random private key, everybody else's private key, and his own private key.
7. Everybody else generates new keypairs and mining starts again, return to step 1
There are issues (for example, what if somebody chooses not to give up their private key after someone else's address is found?), but perhaps it is possible to work around them. This could make a big difference for mining speed, and I'm sure it is worth the downsides.
EDIT: I'm not the first to come up with this, apparently. See https://bitcointalk.org/index.php?topic=1715787.0 by user ArcCsch. When I am done with my current project, I may begin work on a merged-mining pool, and looking into cool aspects of this, for example the most optimised way to split up into smaller merged pools to minimize risk while still keeping profits higher than with "solo" mining.
1. Everybody who wants an address generates an ECDSA keypair, a Personal Pair
2. Everybody gives their public keys to the pool, which combines them into the Combined Public Key
3. The pool distributes the Combined Public Key to miners. The miners generate random keypairs until they find the right address when combined with the Combined Public Key, the same way it's done with split mining.
4. The randomly generated private key is given to the person who requested the address
5. Everybody but the person who requested the address gives their private key to the person who requested it.
6. The person who requested the key can spend funds by combining the pool's random private key, everybody else's private key, and his own private key.
7. Everybody else generates new keypairs and mining starts again, return to step 1
There are issues (for example, what if somebody chooses not to give up their private key after someone else's address is found?), but perhaps it is possible to work around them. This could make a big difference for mining speed, and I'm sure it is worth the downsides.
EDIT: I'm not the first to come up with this, apparently. See https://bitcointalk.org/index.php?topic=1715787.0 by user ArcCsch. When I am done with my current project, I may begin work on a merged-mining pool, and looking into cool aspects of this, for example the most optimised way to split up into smaller merged pools to minimize risk while still keeping profits higher than with "solo" mining.
Please ppl of the internet, prove me wrong, so I can relax...
I am using ccminer 8.13-KlausT...
If I get this message, does it means I found a block(bitcoin)?
GPU #0: bla..bla.. x MH/s
GPU #0: bla..bla.. y MH/s
accepted: 1/1 (100.00%), z MH/s yay!
GPU #0: bla..bla.. x+2 MH/s
GPU #0: bla..bla.. y+3 MH/s
I was solo mining, just for blind-luck and to get some know-how, without any actual goal in mind (in the background while browsing and learning about this crypto-currency hype)
I have a ridiculously small hash power around 150-200 MH/s(BTC), but it is theoretically still possible, like a lottery
...but the hashing went on for like freakin' 20 min. (the excitement was huge) but someone else did the block, and I got no reward...
I am using ccminer 8.13-KlausT...
If I get this message, does it means I found a block(bitcoin)?
GPU #0: bla..bla.. x MH/s
GPU #0: bla..bla.. y MH/s
accepted: 1/1 (100.00%), z MH/s yay!
GPU #0: bla..bla.. x+2 MH/s
GPU #0: bla..bla.. y+3 MH/s
I was solo mining, just for blind-luck and to get some know-how, without any actual goal in mind (in the background while browsing and learning about this crypto-currency hype)
I have a ridiculously small hash power around 150-200 MH/s(BTC), but it is theoretically still possible, like a lottery
...but the hashing went on for like freakin' 20 min. (the excitement was huge) but someone else did the block, and I got no reward...
Sorry to ruin your day but that means you just got a share, not a block
Re: 🔥[ANN] 🔥RUPEE 🔥 RUP🔥 [ANN] 🔥 The New World Crypto Currency has arrived 🔥
MarkaPool for Rupee is back online now that Rupee seems to be actually getting up to speed, after being added to Nova and Yobit. Mine at stratum+tcp://pool.markasoftware.com:17081, more info at http://pool.markasoftware.com and http://pool.markasoftware.com:8080
Re: [ANN] Macroverse - An Entire Universe on the Ethereum Blockchain
Cool concept, but without a working prototype I'm not buying any. Too much like No Man's Sky, and we know how that went 
What kind of prototype are you looking for? There is this prototype deployed on the Ethereum chain right now, and it works.
Here's a listing of the stars in the (0,0,0) sector, from the test suite:
Code:
Stars in origin sector: 39
Star 0 at 0.1613819681097084,18.118419187521795,12.41629295113853 ly is a MainSequence TypeM of 0.13280483893322526 solar masses with planets
Star 1 at 8.352765291169817,21.521832496023308,14.70794403992386 ly is a WhiteDwarf NotApplicable of 0.7937905001253966 solar masses
Star 2 at 23.628362261683833,9.4487003893164,12.631785201278944 ly is a MainSequence TypeF of 1.2172339029093564 solar masses
Star 3 at 17.68796647581894,10.921977819566564,6.6272957395312915 ly is a MainSequence TypeM of 0.09394641004018922 solar masses with planets
Star 4 at 16.616928126040875,16.187588339312242,7.377445674637784 ly is a MainSequence TypeG of 0.9865067396913219 solar masses with planets
Star 5 at 15.74362464036767,6.600803068454297,5.968998394905611 ly is a MainSequence TypeM of 0.26636417300778703 solar masses with planets
Star 6 at 20.268543146312368,14.805240031569156,1.4016471760442073 ly is a MainSequence TypeM of 0.21663218672347284 solar masses with planets
Star 7 at 14.131425873461012,0.8248838812733084,3.87367203904887 ly is a MainSequence TypeM of 0.18189346254075645 solar masses with planets
Star 8 at 4.610691752213825,0.0428331247803726,2.050549116984257 ly is a MainSequence TypeM of 0.181107219693331 solar masses with planets
Star 9 at 21.586779849758386,11.544582400892978,6.165219546960543 ly is a MainSequence TypeM of 0.28534585097804666 solar masses with planets
Star 10 at 13.852605343299729,10.204806822025603,15.587450106386314 ly is a Giant TypeK of 48.90808705718882 solar masses
Star 11 at 13.788190521222532,11.125623866701062,13.996714425388745 ly is a MainSequence TypeM of 0.10444396197726746 solar masses
Star 12 at 21.489885124219654,24.826315800282828,20.456860429499102 ly is a MainSequence TypeM of 0.1178465775492441 solar masses with planets
Star 13 at 4.173886921512349,15.812307129067449,3.7542753055731737 ly is a MainSequence TypeK of 0.7818698770197443 solar masses with planets
Star 14 at 13.27533083747312,16.966044178025186,20.48390676800409 ly is a MainSequence TypeM of 0.2437850927153704 solar masses
Star 15 at 8.736244370561508,1.0378403535241887,9.831296771335474 ly is a MainSequence TypeG of 1.0004645705039366 solar masses with planets
Star 16 at 16.115172616264317,10.567678005190828,10.027809768303086 ly is a MainSequence TypeM of 0.18262802364279196 solar masses with planets
Star 17 at 11.294209219568074,4.3196126885050035,21.229172114317407 ly is a MainSequence TypeM of 0.40833418943748256 solar masses with planets
Star 18 at 5.21207560827861,11.492471201813714,10.38719548073459 ly is a MainSequence TypeM of 0.2684721985224314 solar masses with planets
Star 19 at 18.553889885993158,0.45091477743426367,20.74156241453693 ly is a MainSequence TypeM of 0.4140062171327372 solar masses with planets
Star 20 at 20.23379753577501,17.341250630147442,23.527256473835223 ly is a MainSequence TypeM of 0.26013500826411473 solar masses with planets
Star 21 at 12.66052347978075,8.060563405160792,9.884962858495783 ly is a MainSequence TypeM of 0.2598429443214627 solar masses with planets
Star 22 at 17.307068168952355,20.73634026628497,2.954285925170552 ly is a MainSequence TypeM of 0.27194352844162495 solar masses
Star 23 at 6.862001460854117,20.34844719587454,17.04913473281522 ly is a MainSequence TypeM of 0.33822736503407214 solar masses with planets
Star 24 at 23.699176378659104,14.75463548067637,16.861710910188776 ly is a MainSequence TypeM of 0.21391858288279764 solar masses with planets
Star 25 at 11.07977198385015,4.693625674917712,12.777176997678907 ly is a MainSequence TypeM of 0.4201501412098878 solar masses with planets
Star 26 at 7.363040540849397,10.01761340748999,23.565806943042844 ly is a MainSequence TypeM of 0.3293303501450282 solar masses with planets
Star 27 at 12.371446089809979,8.087426029533162,4.251143996225437 ly is a MainSequence TypeM of 0.11277296043499518 solar masses with planets
Star 28 at 3.1524554843599617,24.93803733898403,10.563421923507121 ly is a MainSequence TypeM of 0.09525545870928909 solar masses with planets
Star 29 at 18.922999667984186,4.089151687594494,21.297638903865845 ly is a MainSequence TypeM of 0.4318041607057239 solar masses with planets
Star 30 at 5.617614002699156,9.960647307684667,22.83705705324337 ly is a MainSequence TypeM of 0.3462359881841621 solar masses
Star 31 at 8.866873133320041,21.352436725965163,9.70895904245026 ly is a MainSequence TypeK of 0.4651559596059087 solar masses with planets
Star 32 at 17.616013039014433,22.401921771574962,24.705373676601994 ly is a MainSequence TypeM of 0.10785482486699038 solar masses with planets
Star 33 at 23.072090780783583,8.107381122158586,0.6762747884749842 ly is a MainSequence TypeM of 0.34945126173624885 solar masses with planets
Star 34 at 16.74501128911743,20.138443240966808,16.374172900964368 ly is a MainSequence TypeM of 0.25525278968689236 solar masses with planets
Star 35 at 12.373427700413231,1.8376803255023333,18.080980920171896 ly is a MainSequence TypeM of 0.44613618154562573 solar masses with planets
Star 36 at 22.86719418109442,18.51714929296122,11.419720619846885 ly is a MainSequence TypeM of 0.4148228889407619 solar masses
Star 37 at 11.30238699226993,12.042864324212132,8.762299942554819 ly is a MainSequence TypeM of 0.20170117294674128 solar masses
Star 38 at 19.951106185339995,14.261220537559893,10.751655614421907 ly is a MainSequence TypeM of 0.3570075996558444 solar masses with planets
Star 0 at 0.1613819681097084,18.118419187521795,12.41629295113853 ly is a MainSequence TypeM of 0.13280483893322526 solar masses with planets
Star 1 at 8.352765291169817,21.521832496023308,14.70794403992386 ly is a WhiteDwarf NotApplicable of 0.7937905001253966 solar masses
Star 2 at 23.628362261683833,9.4487003893164,12.631785201278944 ly is a MainSequence TypeF of 1.2172339029093564 solar masses
Star 3 at 17.68796647581894,10.921977819566564,6.6272957395312915 ly is a MainSequence TypeM of 0.09394641004018922 solar masses with planets
Star 4 at 16.616928126040875,16.187588339312242,7.377445674637784 ly is a MainSequence TypeG of 0.9865067396913219 solar masses with planets
Star 5 at 15.74362464036767,6.600803068454297,5.968998394905611 ly is a MainSequence TypeM of 0.26636417300778703 solar masses with planets
Star 6 at 20.268543146312368,14.805240031569156,1.4016471760442073 ly is a MainSequence TypeM of 0.21663218672347284 solar masses with planets
Star 7 at 14.131425873461012,0.8248838812733084,3.87367203904887 ly is a MainSequence TypeM of 0.18189346254075645 solar masses with planets
Star 8 at 4.610691752213825,0.0428331247803726,2.050549116984257 ly is a MainSequence TypeM of 0.181107219693331 solar masses with planets
Star 9 at 21.586779849758386,11.544582400892978,6.165219546960543 ly is a MainSequence TypeM of 0.28534585097804666 solar masses with planets
Star 10 at 13.852605343299729,10.204806822025603,15.587450106386314 ly is a Giant TypeK of 48.90808705718882 solar masses
Star 11 at 13.788190521222532,11.125623866701062,13.996714425388745 ly is a MainSequence TypeM of 0.10444396197726746 solar masses
Star 12 at 21.489885124219654,24.826315800282828,20.456860429499102 ly is a MainSequence TypeM of 0.1178465775492441 solar masses with planets
Star 13 at 4.173886921512349,15.812307129067449,3.7542753055731737 ly is a MainSequence TypeK of 0.7818698770197443 solar masses with planets
Star 14 at 13.27533083747312,16.966044178025186,20.48390676800409 ly is a MainSequence TypeM of 0.2437850927153704 solar masses
Star 15 at 8.736244370561508,1.0378403535241887,9.831296771335474 ly is a MainSequence TypeG of 1.0004645705039366 solar masses with planets
Star 16 at 16.115172616264317,10.567678005190828,10.027809768303086 ly is a MainSequence TypeM of 0.18262802364279196 solar masses with planets
Star 17 at 11.294209219568074,4.3196126885050035,21.229172114317407 ly is a MainSequence TypeM of 0.40833418943748256 solar masses with planets
Star 18 at 5.21207560827861,11.492471201813714,10.38719548073459 ly is a MainSequence TypeM of 0.2684721985224314 solar masses with planets
Star 19 at 18.553889885993158,0.45091477743426367,20.74156241453693 ly is a MainSequence TypeM of 0.4140062171327372 solar masses with planets
Star 20 at 20.23379753577501,17.341250630147442,23.527256473835223 ly is a MainSequence TypeM of 0.26013500826411473 solar masses with planets
Star 21 at 12.66052347978075,8.060563405160792,9.884962858495783 ly is a MainSequence TypeM of 0.2598429443214627 solar masses with planets
Star 22 at 17.307068168952355,20.73634026628497,2.954285925170552 ly is a MainSequence TypeM of 0.27194352844162495 solar masses
Star 23 at 6.862001460854117,20.34844719587454,17.04913473281522 ly is a MainSequence TypeM of 0.33822736503407214 solar masses with planets
Star 24 at 23.699176378659104,14.75463548067637,16.861710910188776 ly is a MainSequence TypeM of 0.21391858288279764 solar masses with planets
Star 25 at 11.07977198385015,4.693625674917712,12.777176997678907 ly is a MainSequence TypeM of 0.4201501412098878 solar masses with planets
Star 26 at 7.363040540849397,10.01761340748999,23.565806943042844 ly is a MainSequence TypeM of 0.3293303501450282 solar masses with planets
Star 27 at 12.371446089809979,8.087426029533162,4.251143996225437 ly is a MainSequence TypeM of 0.11277296043499518 solar masses with planets
Star 28 at 3.1524554843599617,24.93803733898403,10.563421923507121 ly is a MainSequence TypeM of 0.09525545870928909 solar masses with planets
Star 29 at 18.922999667984186,4.089151687594494,21.297638903865845 ly is a MainSequence TypeM of 0.4318041607057239 solar masses with planets
Star 30 at 5.617614002699156,9.960647307684667,22.83705705324337 ly is a MainSequence TypeM of 0.3462359881841621 solar masses
Star 31 at 8.866873133320041,21.352436725965163,9.70895904245026 ly is a MainSequence TypeK of 0.4651559596059087 solar masses with planets
Star 32 at 17.616013039014433,22.401921771574962,24.705373676601994 ly is a MainSequence TypeM of 0.10785482486699038 solar masses with planets
Star 33 at 23.072090780783583,8.107381122158586,0.6762747884749842 ly is a MainSequence TypeM of 0.34945126173624885 solar masses with planets
Star 34 at 16.74501128911743,20.138443240966808,16.374172900964368 ly is a MainSequence TypeM of 0.25525278968689236 solar masses with planets
Star 35 at 12.373427700413231,1.8376803255023333,18.080980920171896 ly is a MainSequence TypeM of 0.44613618154562573 solar masses with planets
Star 36 at 22.86719418109442,18.51714929296122,11.419720619846885 ly is a MainSequence TypeM of 0.4148228889407619 solar masses
Star 37 at 11.30238699226993,12.042864324212132,8.762299942554819 ly is a MainSequence TypeM of 0.20170117294674128 solar masses
Star 38 at 19.951106185339995,14.261220537559893,10.751655614421907 ly is a MainSequence TypeM of 0.3570075996558444 solar masses with planets
There's a nice G-type star (number 4) that might eventually have some habitable planets, and a relatively rare giant K-type star, and a white dwarf. There's all sorts of gameplay possibilities there; even something as simple as a Noctis clone, where you fly around refueling at white dwarfs, would be pretty fun.
Reading console dumps is not a particularly slick way to explore the universe, so I'm planning to develop a nice front end to let people explore the generated world in a web3-enabled browser, to hopefully be completed before the crowdsale is over. Is that the sort of prototype you're looking for?
Cool, didn't see that. Looking forward to seeing this coin mature. But yeah, some sort of fancy thing is gonna be needed for this to go big, i think most people don't want to buy meaningless coordinates. Also, there should be some super-rare types of things.
Re: [ANN][NKA] INCAKOIN l Perú l Launched Aug 2013 | Roadmap released |
Warning guys! Dev isn't new really a dev! He's asking on xbtfteelancer to get someone to implement new features for him! https://www.xbtfreelancer.com/prj/3987/skilled-developer-required-500-budget-repost
Re: [ANN] XVS - Zerocoin Protocol - PoS 4.0 BETA - Masternode - BlackJack
Hi!
I have problem with you're wallet. Yesterday i have over 210k coins. But after reboot OS balance is 175k coins.. Transactions output nothing. Wallet is synced.
What's going on?
I have problem with you're wallet. Yesterday i have over 210k coins. But after reboot OS balance is 175k coins.. Transactions output nothing. Wallet is synced.
What's going on?
Close the wallet, then relaunch it with the -rescan command line option, it will scan all blocks for transactions to resolve these kinds of issues.
Hello. The wallet doesn't seem to sync completely at this moment; after downloading 100% of the available blocks it reads: 'Catching up.. downloaded 2220 blocks of transaction history. Last received block was generated 13 hour(s) ago.'
And if you check the log, it downloads the first blocks normally and after that last block it just reads 'connection timeout' on ips with 'lastseen' multiple hours ago. As if the whole chain isn't available at this time?
Maybe someone could have a look at this? Thanks!
And if you check the log, it downloads the first blocks normally and after that last block it just reads 'connection timeout' on ips with 'lastseen' multiple hours ago. As if the whole chain isn't available at this time?
Maybe someone could have a look at this? Thanks!
My guess is that nobody is mining the coin anymore so no new blocks are being generated, and the wallet thinks it is behind because latest block is so old.
Re: [ANN][OBC] ObamaCare |live on Exchange | vote and earn Coins| monthly dividends
yeah, im also waiting for the tradesatoshi listing and see how trading goes and how people value this project. 
Tradesatoshi is a small, shitty exchange. Nobody will buy there any more than cryptodao.