|
I have a script which cleans up dust transactions. Basically it combines 49 dust transactions with 1 large transaction using createrawtransaction, signrawtransaction, sendrawtransaction
However it does not seem to work with Clams for some reason...
I keep getting the following error:
error: {"code":-22,"message":"TX rejected"}
After looking into the issue and test sending transactions manually with clamd in a console I get the same error.
Any idea why this might be happening?
It seems to work sometimes if I limit createrawtransaction to using only 2 or 3 input transactions.
On coinwallet.co I have around 7600 dust transactions in the wallet, and am not able to send out even 4 CLAMs with out a "transaction too large" error because of all the dust.
|
|
|
|
|
I see a few options:
1 - They have pulled an exit scam - unlikely I think.
2 - They got hacked and are keeping quiet until they can figure out the extent of the damage and how to move forward.
3 - They are having technical problems, but that would not explain the lack of contact.
|
|
|
|
Added network peers information page for all currencies.  |
|
|
|
Has the block chain stalled? Last block (369857) appears to be 9 hours ago  This issue is of utmost priority to us but lies in the KGW algo when these condition present themselves (from what we know this far). Okay, thanks. I have seen similar behaviour with several other coins using KGW also. |
|
|
|
|
Added live / streaming block info on base currency pages.
|
|
|
|
Has the block chain stalled? Last block (369857) appears to be 9 hours ago |
|
|
|
Are they equal partners in this, or is Markus just working for hire for Fyrstikken? not that it matters - as long as the development goes on ... but i would think when the devs come out and let us know whats happening - maybe we will know what to expect as well ... time - thats all ... they are probably busy with work and their own lives at the moment ...  ... #crysx After taking BTC from investors the least they could do is drop in to the thread now and then and let us know what is going on. agreed ... #crysx Looking more and more like a dodgy ICO... Fyrstikken say it ain't so. |
|
|
|
|
I am trying to get the daemon synced.
After 48 hours, not even a third of the way through...
{
"version" : "v1.3.1.0-1-g63022b6",
"mode" : "full",
"protocolversion" : 60015,
"walletversion" : 60000,
"balance" : 0.00000000,
"shadowbalance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"reserve" : 0.00000000,
"blocks" : 129264
Is this normal?
|
|
|
|
nodes?
Not having any luck syncing.
curious. i never had to manually enter nodes. you could try deleting the peers.dat and restarting wallet. Tried that. No Luck. "version" : "v0.9.1.0-44-g8971bc2",
"protocolversion" : 60013,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 0,
"timeoffset" : 0,
"moneysupply" : 0.00000000,
"connections" : 0, |
|
|
|
|
nodes?
Not having any luck syncing.
|
|
|
|
|
Looks like quite a bit of effort went into the ANN!
|
|
|
|
60% premine!! And you expect us to just trust you that you have the small amount of $36 Million in gold?  |
|
|
|
|
Product looks interesting.
I was going to order 8 x 0.01 BTC coins for fun but the shipping is a bit much for me:
Registered letter / Post packet / UPS delivery: 0,3574 ฿
At current fiat prices that is US$84 to send 4 small coins!
If you are focused on affordability please find cheaper shipping methods.
|
|
|
|
I think the "staking pool" way is the obvious way to go. It lowers variance for everyone. Instead of waiting 8-12 days to stake 1 CLAM, I stake 0.1 CLAMs per day and have a much more regular predictable income.
Working on it now, should be ready in a couple of days. |
|
|
|
Clams has now been added to the CoinWallet.co online wallet service.
That's great news. I'm wondering the same as BayAreaCoins: What percentage of the staking reward do you give to your depositors? Because each currency works off a single client wallet the system works the same as a personal wallet in terms of staking. This means staking rewards are assigned to initial transaction addresses and change addresses. So currently it is a bit of a lottery - but we do not withhold any percentage of the staking reward... I have several ideas to improve this, so users always get 100% of their staked rewards. One way to do it is from the database, so any generated coins get split between all holders dependant on total percentage of mature coins they hold in the system at that point in time. The other is to move to a manual transaction system so change can always come back to the originating address and staking is assigned by address. Each method has its pros and cons. The first method would mean more of a staking 'pool' where all holders of X coin get a percentage of all staking rewards. It's on the todo list. |
|
|
|
block explorer not working?
Strange, I just checked and the explorer is working for me. Uptimerobot.com did not report any downtime either. |
|
|
|
... pay a software licence fee to the company...
This coin will not take off under that model. What will happen, is that all of your technology will be copied and used in a clone that will take off. Of course, you can get around this by making the coin closed source, in which case I doubt you'll ever sell one license fee. I have to agree with drawingthesun. Mining is hard enough as it is without having to pay the devs / parent company / whoever for the privilege. That might make it a hard sell. |
|
|
|
 Clams has now been added to the CoinWallet.co online wallet service. https://www.coinwallet.coRunning since Nov 2013. As always use online wallets with caution and store the majority of your coins in cold storage or a secure / encrypted wallet on your computer. Coinwallet.co serves as an easy to use web based wallet that you can access with just an internet connection. Handy to aggregate your mining income or have a small amount of coins accessible when you don't have access to your main wallet. Free deposits. 0.5% fee on withdrawals. 2 Factor email authentication option on withdrawals. Google Authenticator option on login. |
|
|
|
|
Show Posts
