|
IT'S ALIVE AGAIN!
Someone's Cosmoscoin wallet woke up and happened to connect to my server, which already had cosmoscoin running. With a nearly 6 year gap, the blockchain is suddenly moving again:
19-Jul-2019 14:21:40 UTC+0 height: 2493139 mint: 3.5 difficulty: 0.00391013 flags: proof-of-work tx: 1
19-Jul-2019 14:22:08 UTC+0 height: 2493140 mint: 3.5 difficulty: 0.00392885 flags: proof-of-work tx: 1
19-Jul-2019 14:23:10 UTC+0 height: 2493141 mint: 3.5 difficulty: 0.00394709 flags: proof-of-work tx: 1
19-Jul-2019 14:23:58 UTC+0 height: 2493142 mint: 3.5 difficulty: 0.00394599 flags: proof-of-work tx: 1
19-Jul-2019 14:24:22 UTC+0 height: 2493143 mint: 3.5 difficulty: 0.00395288 flags: proof-of-work tx: 1
05-Apr-2025 01:08:03 UTC+0 height: 2493144 mint: 3081.94 difficulty: 0.00390625 flags: proof-of-stake tx: 2
05-Apr-2025 01:08:12 UTC+0 height: 2493145 mint: 0.24 difficulty: 0.00390625 flags: proof-of-stake|stake-modifier tx: 2
05-Apr-2025 01:08:20 UTC+0 height: 2493146 mint: 0.24 difficulty: 0.00393525 flags: proof-of-stake tx: 2
05-Apr-2025 01:08:43 UTC+0 height: 2493147 mint: 3081.95 difficulty: 0.00396506 flags: proof-of-stake tx: 2
05-Apr-2025 01:09:04 UTC+0 height: 2493148 mint: 0.24 difficulty: 0.00398636 flags: proof-of-stake tx: 2
Fire up your wallets, people! Let's get some staking happening!
# coin: cosmoscoin
addnode=58.216.79.210
addnode=149.28.164.168
|
|
|
|
|
<necrobump>
The blockchain for this coin is still moving. Some addnodes:
addnode=85.15.179.171
addnode=89.185.100.228
addnode=86.100.49.209
addnode=89.185.100.226
addnode=91.206.16.214
addnode=149.28.164.168
Are there any services still alive?
...
Now that I look again, it appears GCN has swapped to a eth token?
|
|
|
|
|
Looks like this is still being mined? I can see starting height growing when restarting the client. My own height is higher than all other peers, so I guess I've forked.
Shout out if you're moving the blockchain?
|
|
|
|
Just out of interest, DEL has mostly been at minimum difficulty (0.00024414) for a couple of weeks. Right now you could mine it with a CPU. With the network still moving, and the difficulty that low, someone probably is using a CPU.
The coin is dead I think? That was my point - the network is still moving, so it is still being mined by someone. (Presumably just batesresearch, but you never know.) FYI, after this post in 2014 surmising the network was on its last legs, the blockchain kept moving for nearly 3 more years. It's now 2025, so if anyone wants to reconnect to a 24/7 deletecoin node: addnode=149.28.164.168 |
|
|
|
2.5 years later, the blockchain hasn't changed from my point of view. Last blocks in October 2019. My coin server is back up 24/7 now, but there's been no obvious connection attempts over the past couple of weeks. Anyone want to get out their old client? addnode=149.28.164.16823-Oct-2019 07:27:25 UTC+0 height: 2167394 mint: 64 difficulty: 0.00024414 flags: proof-of-work tx: 1 hash: 00000e9e1bd6aec47e49fa799f2dd8a8aaba952df932f6e2a6dddff58061f2f3
23-Oct-2019 07:27:28 UTC+0 height: 2167395 mint: 64 difficulty: 0.00024414 flags: proof-of-work tx: 1 hash: 00000073ab61335df0073509436681de14a49af5005ef704d5c96c825b4989b9
23-Oct-2019 07:27:30 UTC+0 height: 2167396 mint: 64 difficulty: 0.00024414 flags: proof-of-work tx: 1 hash: 00000445e9d1d1e163f22a9c43a35a0f6ce4a75be176f6fd0141e5729839d286
23-Oct-2019 07:27:37 UTC+0 height: 2167397 mint: 64 difficulty: 0.00024414 flags: proof-of-work tx: 1 hash: 00000cab4f821756aad374bb4c475c77043ed1e20317d5e4bbffba3922941369
23-Oct-2019 07:27:52 UTC+0 height: 2167398 mint: 64 difficulty: 0.00024414 flags: proof-of-work tx: 1 hash: 00000cf7f9f92011a28f953d00b3c83a168bc899b305c30234e4b355421ac8b7
23-Oct-2019 07:27:56 UTC+0 height: 2167399 mint: 64 difficulty: 0.00048827 flags: proof-of-work tx: 1 hash: 000005ffc6a4a5536cc99d0a876eb904a731ae7608c7367c90cc29b713459a10
23-Oct-2019 07:28:03 UTC+0 height: 2167400 mint: 64 difficulty: 0.00097655 flags: proof-of-work tx: 1 hash: 00000396a519e7dbf50fba7bec687a7675a55a3ac36c515bf6adb3f705641ea6
23-Oct-2019 07:28:53 UTC+0 height: 2167401 mint: 64 difficulty: 0.00195311 flags: proof-of-work tx: 1 hash: 0000012e9c1609b62ea414c209bd6f255bfde589dfc79e72e32988c6c69c53fc
23-Oct-2019 07:29:40 UTC+0 height: 2167402 mint: 64 difficulty: 0.00390625 flags: proof-of-work tx: 1 hash: 000000dcb0fa87829d9249dcb40b93f26ebe7bd7d19b06fa5626cbb1e0d9b0b6
23-Oct-2019 07:29:55 UTC+0 height: 2167403 mint: 64 difficulty: 0.0078125 flags: proof-of-work tx: 1 hash: 0000007a36288715c92dd044d4849f51adb5e59d3e052544cc7b0a6cb57b1e5b
23-Oct-2019 07:30:52 UTC+0 height: 2167404 mint: 64 difficulty: 0.01531863 flags: proof-of-work tx: 1 hash: 0000000287521d3186d3b994519b68bc7cc1fda3b333bb6dda355758b26aa7ed
|
|
|
|
|
I have a blockchain that was last added to nearly 11 years ago:
08-Nov-2014 10:12:15 UTC+0 height: 107083 mint: 0.008049 difficulty: 0.00390625 flags: proof-of-stake tx: 2 hash: 807414cc0d4fcb124a0d72ffc03ef5c4e046c92fe4ca835392465e32e3c2b8c8
08-Nov-2014 18:37:18 UTC+0 height: 107084 mint: 0.008952 difficulty: 0.00390625 flags: proof-of-stake tx: 2 hash: aa2003739012e87219637e2c6a7b46594a6ac1daacd35ce731dff9b4b690f68e
08-Nov-2014 19:50:56 UTC+0 height: 107085 mint: 0.009117 difficulty: 0.00390625 flags: proof-of-stake|stake-modifier tx: 2 hash: 35b815c5a81199d7abe07de1841166f1624f32cfd5bfc4026f879f5d46d6327f
09-Nov-2014 01:14:45 UTC+0 height: 107086 mint: 0.00887 difficulty: 0.00390625 flags: proof-of-stake tx: 2 hash: 139caa238fbdea7538e552958f4eb0270bbc211747cc1a17888a84503899bef1
09-Nov-2014 04:05:32 UTC+0 height: 107087 mint: 0.009035 difficulty: 0.00390625 flags: proof-of-stake|stake-modifier tx: 2 hash: 231941d7d67a83d470e7c6411cbc61af9ed2dab90a55a1fb678bf86912736ad5
09-Nov-2014 14:38:52 UTC+0 height: 107088 mint: 0.008788 difficulty: 0.00390625 flags: proof-of-stake tx: 2 hash: 382cab65ad7563d8b6d2658776ee2d8986516f8e348237b72947ea4fcc711c50
09-Nov-2014 18:40:15 UTC+0 height: 107089 mint: 0.008952 difficulty: 0.00390625 flags: proof-of-stake|stake-modifier tx: 2 hash: 784a1e58ecc8f23f632da4ec1a58e045ba4fef8a61981a83817985ea72d1beca
09-Nov-2014 18:55:48 UTC+0 height: 107090 mint: 0.008788 difficulty: 0.00390625 flags: proof-of-stake tx: 2 hash: 68b45df658c73749dab5176148c87b3546298f7da9e8c10b2ed36e968ceeebd7
09-Nov-2014 20:29:19 UTC+0 height: 107091 mint: 0.009035 difficulty: 0.00390625 flags: proof-of-stake tx: 2 hash: e6e552dd94c217593df10ed4c15fb2a13e9e4d87c6bd92091229452dd68bf166
My newest transaction has 5225 confirmations, so at least 5225 blocks at the tip were generated by others.
Did the blockchain ever get extended beyond this point?
|
|
|
|
|
My coin server has been powered off for some time due to hardware failure, but I'm now running it as a VM on another machine. If anyone wants to dig out their StarCoin client, and sync up:
addnode=149.28.164.168
|
|
|
|
I'm trying to build v2.1.0-beta.1
Had numerous problems with Boost, had to try several different versions just to get anywhere near a successful compile, and still had to make some minor mods to the source (now pushing 6 years old) to work on a current compiler.
With clang, it dumps core with an illegal instruction
With gcc, the final link fails
I've spent wayyy too much time on this. Can someone who has compiled it tell me their exact setup? Most interested in boost version, but other info would help. Thanks.
We use the compiled version on https://github.com/nochowderforyou/clams/releases/tag/v2.1.0-beta.1We trust it because X did that version  Not sure how this helps answer my question... That's our exact setup. (Just relaying what X said about compiling it on your own, he said your original post could have 1000 things wrong and he said he just uses the "complied version". *shrugs*) Sorry, I have no idea who or what X is. I can't use a precompiled version because I don't run a supported OS. Thus the specific question about setups. |
|
|
|
I'm trying to build v2.1.0-beta.1
Had numerous problems with Boost, had to try several different versions just to get anywhere near a successful compile, and still had to make some minor mods to the source (now pushing 6 years old) to work on a current compiler.
With clang, it dumps core with an illegal instruction
With gcc, the final link fails
I've spent wayyy too much time on this. Can someone who has compiled it tell me their exact setup? Most interested in boost version, but other info would help. Thanks.
We use the compiled version on https://github.com/nochowderforyou/clams/releases/tag/v2.1.0-beta.1We trust it because X did that version Not sure how this helps answer my question... |
|
|
|
|
I'm trying to build v2.1.0-beta.1
Had numerous problems with Boost, had to try several different versions just to get anywhere near a successful compile, and still had to make some minor mods to the source (now pushing 6 years old) to work on a current compiler.
With clang, it dumps core with an illegal instruction
With gcc, the final link fails
I've spent wayyy too much time on this. Can someone who has compiled it tell me their exact setup? Most interested in boost version, but other info would help. Thanks.
|
|
|
|
still alive?
nodes info?
Had the client running a day or two, here's what it found. Both IPs accept inbound connections. Hope this helps. # coin: batcoin
addnode=185.87.149.61
addnode=91.206.16.214
|
|
|
|
Link 404? Other repositories under that account seem to be cracking based, with executables only... so yeah, nah. |
|
|
|
Seriously, how stupid is someone to use SHA256("") More likely to be a programming error. I recall suggesting a few years ago in this thread that something like (pseudoish code) assert(key != 0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855) would have avoided this particular issue. |
|
|
|
Use the coinmarketcap site for such details and use the exchanges for trading purpose, there are exchanges which is giving the details you are looking for but how do you end up getting those altcoin in first before even doing basic information about them?
I'm mining, not investing, thus I want to find some new (preferably obscure) coins to play with. That's why I specified that I didn't want any ERC20 tokens. I currently have 166 coin clients installed, but most of their blockchains are dead, and very few are still listed on an exchange. I'd prefer to find an exchange I like and work backwards to see what coins they have available, rather than find a coin via a third party then figure out the exchange(s) to use for it. I know it seems like a weird approach, but remember my perspective is like that of a multipool operator, rather than a retail investor. |
|
|
|
A link posted by a newbie to a github rep that only has executables, and no source? That's a pass from me... |
|
|
|
Mini privkeys
I wanted to understand how it's calculated and I was told that when the there's a product,if the very first byte results to `00', it's well calculated.
Question:
+Since the SHA256 hash is calculated just by the selection process of random numbers, which forms a polynomial and prolly an interger, what's the probability of getting an `00' just by choosing at random?
What a strange coincidence, I just bumped/updated a 3 year old post of mine with information about mini private keys, and then I find your thread started 7 hours earlier. See: https://bitcointalk.org/index.php?topic=4768828.msg60704068#msg60704068The search space even for the less secure mini private key is still massive (58^22, I guess?). Any attempts at cracking would be an academic curiosity rather than a way to make (ie: steal) funds. As for cracking a 256 bit private key directly, fuggedaboudit. The exception being weak keys (like the top 240 bits being all zero) that are used for fun and occasionally by mistake. |
|
|
|
I thought the mini private key format, used for Casascius physical bitcoins should rate a mention here, because it's basically a SHA256 brainwallet... but with a randomly generated passphrase. https://en.bitcoin.it/wiki/Mini_private_key_formatGiven that the random passphrase length is 22 characters (early version) or 30 characters, the chances of brute forcing it are still virtually nil, but technically, it is less secure than a standard key, in particular because 99%+ of the tries can be discarded after the first SHA256 hash. I came across my simple mini key generator tonight, and I'm having another play with it. The naive version uses random() and outputs about 8000 valid keys per second on a single core of an i7-3960X. I updated it to use the xoshiro256** PRNG, and the speed increases to around 13000 valid keys per second. Because the generation process requires that the first byte of the candidate hash be '00', on average only 1/256 candidates will be valid, so it's really testing about 3.3 million keys per second. It's still a massive search space (58^30?), even for a SHA256 brainwallet, and prematurely discarding 255 out of 256 candidates does not reduce the search space... it just makes searching faster. Plus, how many Casascius coins were ever created, and how many would still be funded? So this is really just a curiosity. Here's a small sample of randomly generated valid keys: S8Q2r4p3HKtDGYXYgcoE6N
SAN7cS1MnFNps25QHt4pRk
SCG9csSvqn2kytKW1WdNd6
SCzCTefJ7J7iGsz4XbMhU6
SFHwkzYdQgDVdhHSdGmCxCZN8YQiNT
SFikz2eev6PMNhU9JNo1DAJ2bcdvSL
SKNzLVj4LHzG8C95ZpjFL5X8HDZNyx
SKgC6zF8opjFQqHhL2Nud1Qx5FpsBc
SN5FSGaCVahVDmM7ARQgijwTExfsWK
SP41nfQVpTpFqfaPUREfBu
SPHPyjWYQKzwrw4bW4ckwwhGNvkSo1
SPpof8XT1ZfrjFBqMaqqN9tuaJ6SyL
SQHv63Wu43viTu2CnbWasR
SQpKTKp1t1phNgg4Qt8piwGxsCxxp1
SQqX32iniiKPqhVbFsuK5RQWqnHUnu
SUZNCr2iXiA4B9qiLVAWJEmMC9LfUj
SWyMZq87mrvSqjiU3KRJ7CbXKtEW6A
SZLdpNMFDfnxMSLKXmaUckAgXMuLXL
Sai3S1jgnN5E2QoydQAVr7u4U3KYFU
Sc9wTknTRqXUTSkB8pFWbX
SdUecesqKtj77JhrQT4obAt5XnCScf
SdXNZMq45NZGdYGzb7UnCe
Sdc3fyobJE2AAKxSLvnYia
The private key is simply the SHA256 hash of the string, like a brainwallet. Some useless information, but hopefully it might kickstart the thread again.  |
|
|
|
|
I am on the hunt for new exchanges that service altcoins with a dedicated blockchain and a dedicated client (ie: not ERC20 tokens)
One of the nice things about Novaexchange (now closed) is that for each coin it included such information:
1. The coin name and ticker
2. The coin icon/logo
3. A link to the coin's official website
4. The blockchain height
5. A page with a list of current peers
6. A link to the github source
Many exchanges only show #1 and #2, at most.
With some coins having ambiguous names and/or ticker symbols, you could be confident with this extra information that you and the exchange were both using the exact same coin, and your client was properly synced relative to the exchange's client.
Curious if any currently open altcoin exchanges provide this level of detail?
|
|
|
|
addnode=67.189.193.76:18216
It's about 6 hours later, nothing listening on that IP/port? Try addnode=149.28.164.168 |
|
|
|
Just because there are people still mining this dead coin, doesn't mean it has any value. It's numbers for numbers sake. A billion grains of sand are as worthless as 100 grains, if no one has use for or can use that sand. Same, too, for Teacoin. An intrinsic purpose has to be given to it, for it to have any value... to anyone.
Uh, okay. Guess your feelings have changed over the past 3 years. |
|
|
|
|
Show Posts
