Speaking of the wallet.
I just sent 3800 INK 7 hours ago, and the wallet show this:
Status: 0/unconfirmed
Date: 2/26/2014 14:47
To: [private]
Debit: -3800.00 INK
Transaction fee: -0.0001 INK
Net amount: -3800.0001 INK
Transaction ID: fc653b2bbe859c01b5393406587da0aab92b6a26b6ad6547d35ee6ec53c1c1c8
And that TX ID doesn't show in the blockchain.
Did the wallet just robbed me of 3800 INK? That would be fun...
Happened to me too, but with 15300 INK. I tried various things: restarting wallet, exporting and importing private key (usually worked for me in such cases, but not here), -salvagewallet (2/3 of my remaining money disappeared, fortunately I had a backup), but couldn't get the INKs back. Finally after a while I solo-mined a block and then this transaction got included in this block and sent to the network. Hope you get a happy ending as well. Thanks for the answer. I just exported the privkey, backed up the wallet, deleted the blockchain and started e full resync before importing. But now I have low hopes for this. Maybe solomining, but on this diff my Phenom X6 1045T will prolly never find a block. That is some buggy wallet, never happened to my before. |
|
|
|
|
Speaking of the wallet.
I just sent 3800 INK 7 hours ago, and the wallet show this:
Status: 0/unconfirmed
Date: 2/26/2014 14:47
To: [private]
Debit: -3800.00 INK
Transaction fee: -0.0001 INK
Net amount: -3800.0001 INK
Transaction ID: fc653b2bbe859c01b5393406587da0aab92b6a26b6ad6547d35ee6ec53c1c1c8
And that TX ID doesn't show in the blockchain.
Did the wallet just robbed me of 3800 INK? That would be fun...
|
|
|
|
Dev, update the wallet to make it stabler!!
Maybe you need to add more node IPs? the 146.185.173.146 connection is too huge.... so, we need more node. The NXT-E guys complained repeatedly in the chatbox that the ink wallet gets stuck (doesn't sync) from time to time and needs restarting. Maybe you should look into that before it hits one more exchange and it meets with similar problems. That could compromise adoption from other exchanges and damage the coin. Good luck! |
|
|
|
I understand it was DarkComet RAT (Remote Administration) Anyone that got infected can use the DarkComet RAT Remover made by phrozensoft: https://phrozensoft.com/processdl_5.htmlAnd next time use either a virtual machine or something like Sandboxie. |
|
|
|
I really like this idea. Almost everyone can mine. And the fast launch is a great way to give a chance to the little miner. Thank you, dev guy!  |
|
|
|
+1 A few reasons: + New algo, CPU mined, no premine, no nonsense. + Few people reported some quirks, but overall reception was pretty good. + No pre-ann means that the usual CPU farms and botnets were not prepared for the launch, giving normal people (at least those that were paying close attention to new launches) a chance to mine on low diff. + Right now the diff is skyrocketing at a rate of 4x per step up, so it's getting harder and harder to mine, more the reason to believe it will get traded. + Almost zero marketing means that adoption was as "grass roots" as it gets. I believe the INK community deserves a chance.
|
|
|
|
Interesting. Takes guts to post an IPO the same day as stack failed. |
|
|
|
Anyone selling this coin at 2 Satoshi, I will take it.
O RLY mate? There's only 11 million of them + new algo, there's gotta be some value to that. If people like this coin and the dev doesn't do anything scammy or stupid, I see it going towards 10k satoshi EDIT: Also, keeping the early dumps to a minimum would help. |
|
|
|
A lot of people whining here
I started about 20 minutes after the launch with my modest i5 4 cores and a got thousands of INK. You, guys simply didn't figured out how to reduce the chances of getting orphans, being on a low latency node or adding all the nodes possible.
If you are out of the game, what you need is assistance/guidance, whining is useless.
+1 Also, some of your advice on how to reduce the chances of getting orphans and being on a low latency node would be appreciated |
|
|
|
|
I wonder what is the total network hash/s
Couldn't get it in the console, the usual method (getnetworkhasps) is not implemented
|
|
|
|
|
For everyone with slow sync:
Try setgenerate false until sync complete, then setgenerate true.
It seems to speed up things a bit.
|
|
|
|
And one block for you. Let's spread the love. |
|
|
|
orphanfest... I would appreciate if someone will send me several coins  : 1AuuiqurrJNVp7Br1t6ivoHJ8YeyeoJ8i1 There you go mate, 1 block worth of coins for you Orphan city. Anyone on the main chain wanna share some love? 1B3ask119JdHE9jUzPLX4TDa5q6Vs4f5ye And one block for you, sir. I really like this coin. New algo, no PRE-ANN, no pools or optimized miners yet, just a man and his CPU. And the peer list, ofc. Feels like the good ol' days.  |
|
|
|
I can't even get the wallet to sync never mind mine anything
Stop the wallet add the peers I posted above start the wallet go to debug console give this command: addnode 146.185.173.146 onetry  profit |
|
|
|
Fresh peers: addnode=188.165.221.211:1216
addnode=198.204.228.10:1216
addnode=64.79.77.26:1216
addnode=36.57.202.139:1216
addnode=175.156.218.76:1216
addnode=82.100.88.88:1216
addnode=84.54.172.18:1216
addnode=101.16.132.166:1216
addnode=78.128.69.66:1216
addnode=108.62.194.44:1216
addnode=90.157.19.238:1216
addnode=36.248.127.99:1216
addnode=144.76.59.202:1216 |
|
|
|
Does anyone have any other nodes I can add? I seriously can't get the wallet to sync - "No Block Source Available". I've got the conf file set up correctly (not .txt) and from the 20+ wallets I've set up, this is the first time I've ever had this issue. Advice / extra nodes welcomed Did you tired the node form nodes.txt ? addnode 146.185.173.146 onetry |
|
|
|
11:28:21

{
"blocks" : 1901,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.06249911,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 165115,
"pooledtx" : 0,
"testnet" : false
}
What? Hardfork already?  { "blocks" : 8390, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.06249911, "errors" : "", "generate" : true, "genproclimit" : 4, "hashespersec" : 925774, "pooledtx" : 0, "testnet" : false } it it is I'm on the same branch.  { "blocks" : 9051, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.06249911, "errors" : "", "generate" : true, "genproclimit" : -1, "hashespersec" : 844047, "pooledtx" : 0, "testnet" : false } |
|
|
|
|
I see. I got 22 confirmed. The rate of orphaned seems to decrease.
|
|
|
|
|
Exactly the same here. Tons of blocks, almost immediately orphaned.
EDIT: 2 blocks somehow got confirmed
|
|
|
|
|
Show Posts
