[ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"

[Vin]

where you can download fresh bootstrap 

https://bitcointalk.org/index.php?topic=623147.msg9772191#msg9772191

[1714870473]

1714870473

[1714870473]

1714870473

[dooglus]

where you can download fresh bootstrap 

I just uploaded a new one. See the post the previous two posts both directed you to - I edited it a minute or two ago.

[1qaz]

where you can download fresh bootstrap 

I just uploaded a new one. See the post the previous two posts both directed you to - I edited it a minute or two ago.

thx ^ ok im again try use new bottstrap files  .....


but


Last time using bootstrap from July 7 or 11 , had a bug stop import blocks on height=1781476

[dooglus]

Last time using bootstrap from July 7 or 11 , had a bug stop import blocks on height=1781476

Do you have a link to your github issue?

[1qaz]

i no have github acc


48 hours waits and again stop on 1781476 import from bootstrap ((((


bad

[Rodrick12]

Now they refunded the failed withdrawal, I proceeded with another one, and also this one shows as "COMPLETE" with txid, but the txid is not present on the explorer.
I have had several mishaps with CLAMs on Poloniex in the past, but this time is starting to get ridiculous... And yes, replies from the customer care team are void of useful information.

I've also experienced it like you, and I don't understand what really happened, I sent a ticket to their team but there was no reply at all maybe someone can help me here

I'm also starting to get no replies from the support. And my CLAMs are still in the limbo. I don't think any help can come if not from Poloniex itself, but they seem not to care much.

But maybe the experts here could provide some speculation on how it can happen that Poloniex got and provided us with a txid, but the transaction doesn't even appear on the explorer: That's a complete mystery to me!

[1qaz]

Last time using bootstrap from July 7 or 11 , had a bug stop import blocks on height=1781476

Do you have a link to your github issue?

logs

10:16:00
ProcessBlock: ACCEPTED
bool LoadExternalBlockFile(FILE*)() : Deserialize or I/O error caught during load
Loaded 1781476 blocks from external file in 114327805ms
dumpaddr thread stop
addcon thread interrupt
opencon thread interrupt
msghand thread interrupt
net thread interrupt
Shutdown : In progress...
StopNode()
Shutdown : done

[dooglus]

Last time using bootstrap from July 7 or 11 , had a bug stop import blocks on height=1781476

Do you have a link to your github issue?

logs

10:16:00
ProcessBlock: ACCEPTED
bool LoadExternalBlockFile(FILE*)() : Deserialize or I/O error caught during load
Loaded 1781476 blocks from external file in 114327805ms
dumpaddr thread stop
addcon thread interrupt
opencon thread interrupt
msghand thread interrupt
net thread interrupt
Shutdown : In progress...
StopNode()
Shutdown : done

Can you provide the sha256 hash and file size of the bootstrap.dat file you're trying to use?

[1qaz]

Last time using bootstrap from July 7 or 11 , had a bug stop import blocks on height=1781476

Do you have a link to your github issue?

logs

10:16:00
ProcessBlock: ACCEPTED
bool LoadExternalBlockFile(FILE*)() : Deserialize or I/O error caught during load
Loaded 1781476 blocks from external file in 114327805ms
dumpaddr thread stop
addcon thread interrupt
opencon thread interrupt
msghand thread interrupt
net thread interrupt
Shutdown : In progress...
StopNode()
Shutdown : done

Can you provide the sha256 hash and file size of the bootstrap.dat file you're trying to use?

3D45796F2AEF6FD665B974C81859B51E6869BB17E803EBBA322794E87BC4B097

size - 3 265 405 kb

[dooglus]

Can you provide the sha256 hash and file size of the bootstrap.dat file you're trying to use?

3D45796F2AEF6FD665B974C81859B51E6869BB17E803EBBA322794E87BC4B097

size - 3 265 405 kb

I just created a new copy of the bootstrap.dat for blocks 0 through 2654600 from an independent CLAM node. It has the same sha256 hash as your copy, so I'm sure your copy is correct.

I don't know what the problem could be here. Are you putting the bootstrap.dat file into the correct folder with the correct name? It should go in the same folder as your CLAM wallet.dat file, and be called bootstrap.dat all in lower case.

Did anyone else try syncing the blockchain recently using this bootstrap.dat file? Did it work for you?

[Davidbike1]

Clams sure fell hard since May 26th  , but I am happy to see the price now picking up over the past couple of days 

[smooth]

Clams sure fell hard since May 26th  , but I am happy to see the price now picking up over the past couple of days  

That peak was likely the result of a single buyer or a small group manipulating the market, probably for the purpose of ripping off Poloniex through their dumb margin system (and given Poloniex's response to it, ultimately ripping off Poloniex's other users).

It you disregard that outlier pump CLAM is actually doing pretty well, considering market conditions. It's price in satoshis is actually higher than where it was late last year, which is not the case of a lot of well-known coins like ETH or XRP.

[almightyruler]

I'm also starting to get no replies from the support. And my CLAMs are still in the limbo. I don't think any help can come if not from Poloniex itself, but they seem not to care much.

But maybe the experts here could provide some speculation on how it can happen that Poloniex got and provided us with a txid, but the transaction doesn't even appear on the explorer: That's a complete mystery to me!

I speculated earlier in this thread that the CLAM client's wallet could be corrupt in some way, so the client was occasionally generating transactions that appear to be good from Poloniex's side, but in reality are double spending. Such transactions will be immediately rejected by the network, and will never confirm.

After experiencing my own stuck withdrawal, I'm less inclined to think it's that, because the txid they provided at withdrawal time is the exact same transaction that made it to the network (eventually).

I wonder if it could be related to the problems that CLAM has with syncing from the network.

Frontend support is polite but effectively useless for more complicated issues. There doesn't seem to be any interest in discussing the problem, let alone fixing it. I reported a minor issue with the API and the reply basically just reiterated the problem without committing to a fix.

[Rodrick12]

I'm also starting to get no replies from the support. And my CLAMs are still in the limbo. I don't think any help can come if not from Poloniex itself, but they seem not to care much.

But maybe the experts here could provide some speculation on how it can happen that Poloniex got and provided us with a txid, but the transaction doesn't even appear on the explorer: That's a complete mystery to me!

I speculated earlier in this thread that the CLAM client's wallet could be corrupt in some way, so the client was occasionally generating transactions that appear to be good from Poloniex's side, but in reality are double spending. Such transactions will be immediately rejected by the network, and will never confirm.

After experiencing my own stuck withdrawal, I'm less inclined to think it's that, because the txid they provided at withdrawal time is the exact same transaction that made it to the network (eventually).

I wonder if it could be related to the problems that CLAM has with syncing from the network.

Frontend support is polite but effectively useless for more complicated issues. There doesn't seem to be any interest in discussing the problem, let alone fixing it. I reported a minor issue with the API and the reply basically just reiterated the problem without committing to a fix.

Thanks, that's informative. So at the root it might be an issue with the CLAM network, or, as one could infer from Poloniex reported answer on this Reddit post (https://www.reddit.com/r/poloniex/comments/ax03k0/clam_withdrawal/), a lack of miners??

[almightyruler]

Thanks, that's informative. So at the root it might be an issue with the CLAM network, or, as one could infer from Poloniex reported answer on this Reddit post (https://www.reddit.com/r/poloniex/comments/ax03k0/clam_withdrawal/), a lack of miners??

No. "As soon as a miner picks up the transaction" seems like a generic response, and is false anyway, since the stuck transactions do not seem to appear on the network. (All CLAM clients, including block explorers, can see pending mempool transactions which have not yet been incorporated into a mined block). On top of that, since CLAM is a PoS only coin, anyone who has the client open with a balance can mine blocks, so there's certainly no issue with block generation.

[dooglus]

Thanks, that's informative. So at the root it might be an issue with the CLAM network, or, as one could infer from Poloniex reported answer on this Reddit post (https://www.reddit.com/r/poloniex/comments/ax03k0/clam_withdrawal/), a lack of miners??

Have them copy/paste the raw hex transaction into the form here:

https://just-dice.com/pushtx

Then it will confirm very quickly.

[Rodrick12]

Thanks, that's informative. So at the root it might be an issue with the CLAM network, or, as one could infer from Poloniex reported answer on this Reddit post (https://www.reddit.com/r/poloniex/comments/ax03k0/clam_withdrawal/), a lack of miners??

Have them copy/paste the raw hex transaction into the form here:

https://just-dice.com/pushtx

Then it will confirm very quickly.

Thanks for the advice! I'm not expert, but if we have the txid, couldn't we do that ourselves? I guess we would just need to convert the txid into hex (I'm not sure how/if it is possible, though...), right?

[almightyruler]

Thanks, that's informative. So at the root it might be an issue with the CLAM network, or, as one could infer from Poloniex reported answer on this Reddit post (https://www.reddit.com/r/poloniex/comments/ax03k0/clam_withdrawal/), a lack of miners??

Have them copy/paste the raw hex transaction into the form here:

https://just-dice.com/pushtx

Then it will confirm very quickly.

From some quick hunting around, it seems that Bitcoin Core may accept but not broadcast a valid (signed) raw transaction until it is fully synced. I haven't been able to fully confirm this yet, but did observe this myself when trying to broadcast a Bitcoin transaction from two non-synced clients (nb both were synced well past the input transaction).

If this same behaviour is present in the CLAM client, this may explain why real txids are being shown to Poloniex customers, but the transactions don't immediately make it out to the network: the Poloniex CLAM client is not reliably syncing.

[tonyvo2017]

To get clams, do I need to make PoC or PoWS in your wallet?
or anywhere else in the wallet? Please guide me.

[seoincorporation]

To get clams, do I need to make PoC or PoWS in your wallet?
or anywhere else in the wallet? Please guide me.

Clam is a PoS (proof of stake) coin, you can mine with your wallet and this process is known as staking. But the main rule to make staking is to hold some clams in your wallet, the number of the stacking clams you hold VS the number of staking clams in the network is like the hash rate you have in the network.

If you want to learn more about staking please read the next link: https://gist.github.com/abmohan/f7c3dfecbffb996e37dea052fac0fb9e