|
got a reply from bittrex:
"Hi,
Thank you for the information.
Ryan"
if enough of us have done it hopefully they'll sort it out
|
|
|
|
Just so everyone knows, I have been speaking with Bill at Bittrex about addition and this is his concern. I've had a trusted consultant of ours say that they got rejected by you for their free coins which in my mind casts significant doubt on what you are doing Whoever is lying to them about not getting their coins.... you, sir, are a straight up douchebag. Whoever did receive their coins, please email support@bittrex.com and let them know you received your coins as were promised. Whoever is lying to exchanges, stop being an asshole, pleasewhat a dick, don't understand bittrex listening to one disgruntled twat. Coins received yesterday, emailing bittrex now |
|
|
|
didnt receive any cube yesterday  have i missed distribution? |
|
|
|
|
17:51:32

getpeerinfo
17:51:32

[
{
"addr" : "24.160.59.242:13370",
"services" : "00000001",
"lastsend" : 1447609872,
"lastrecv" : 1447609885,
"conntime" : 1447609428,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 241232,
"banscore" : 0
},
{
"addr" : "81.107.187.223:50685",
"services" : "00000001",
"lastsend" : 1447609885,
"lastrecv" : 1447609885,
"conntime" : 1447609431,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 241231,
"banscore" : 0
},
{
"addr" : "104.209.32.223:39488",
"services" : "00000001",
"lastsend" : 1447609885,
"lastrecv" : 1447609885,
"conntime" : 1447609475,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 241235,
"banscore" : 0
},
{
"addr" : "194.135.93.51:39872",
"services" : "00000001",
"lastsend" : 1447609885,
"lastrecv" : 1447609885,
"conntime" : 1447609487,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 241235,
"banscore" : 0
},
{
"addr" : "83.135.119.56:53974",
"services" : "00000001",
"lastsend" : 1447609872,
"lastrecv" : 1447609883,
"conntime" : 1447609545,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 241237,
"banscore" : 0
},
{
"addr" : "5.9.36.211:54950",
"services" : "00000001",
"lastsend" : 1447609872,
"lastrecv" : 1447609883,
"conntime" : 1447609872,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 241254,
"banscore" : 0
}
]
|
|
|
|
|
new sigs much better than last, good job
|
|
|
|
think i f'fed up... new to nxt didn't realise i'd have to use the wallet before its useable! bought some nxt at trex and tried to withdraw putting public key in the message box but it keeps coming back as invalid 1. Which client do you use? Which OS? 2. How did you create your account? Remember, passphrase is your account. Always double check that your pasphrase opens the same account. Small mistake in passphrase (lowercase, missed character, etc.) will open new account. That's how brain wallet works. thanks for your reply logging into my account was fine its the using it that was the problem (activating it with a transaction) but i found this site http://jnxt.org/key which has sorted me out  |
|
|
|
think i f'fed up... new to nxt didn't realise i'd have to use the wallet before its useable! bought some nxt at trex and tried to withdraw putting public key in the message box but it keeps coming back as invalid |
|
|
|
pm sent new to nxt so this will be an experience |
|
|
|
https://mega.nz/#!bxV2DQqD!0NuCrgDbxEa-lkh-608NxASTYBb9GN9s3yIE0yDjAbY is the wallet download link is this an updated wallet? |
|
|
|
 couldn't resist |
|
|
|
i like it  |
|
|
|
can someone send me a few, downloading the wallet.. i like this, my r9's farm x13 pretty well.
thanks!
current block 16397 Block 15841 - 17280 = 0.1337 [1337] there really isn't any point in mining ... and please remove the address its against the rules |
|
|
|
So, you mean, PoS not base on percent, but PoS 1 XMT / Block? Am I right?
yes mate that's correct so what we have is another opportunity to cut down supply  |
|
|
|
When staking, would it stake faster if had 5 addresses with 1000 coins each or 1 address with 5000 coins?
it would stake faster in one lump but you'd get more blocks with it split probably higher rewards when combined. Also good news when there's tx fees to be had personally I'm just allowing mine to split with each stake and keeping it in the one address |
|
|
|
How PoS % (Percent) per year?Day?Month?Hour?
Thank you...
in the op
Algo: Scrypt PoW/PoS Hybrid
Difficulty Retarget: Every Block
POS Reward: 1 XMT / block
Block Time: 1 Minute
Block Maturity: 100 Blocks
RPC Port: 29028
Total Coin Supply: 70,000,000 XMT
Premine: (ICO*) - Block 1: 55,000,000 XMT
Week 1: (ICO Period) - Block 2-11,000: 1 XMT/block - (10999 XMT)
Month 1: Block 11,001 - Block 54200: 115 XMT/block - (4,967,885 XMT)
Year 1: Block 54201 - Block 579801: 9.5 XMT/block - (4,993,200 XMT)
Year 2-5: Block 579801 - End of Life: 2 XMT/block - (4,000,000 XMT)
*Unsold ICO coins will be burned. 5,000,000 XMT of the premine will go to the development fund as incentive to keep the devs active and engaged, as well as to be used for incentives and marketing
*update 11/4* We will burn the development premine to match the percentage of the ICO that is sold. EX: if we only sell 10% of the ICO, we will burn 90% of the development premine.
|
|
|
|
|
coins received but
problems???
wallet out of sync last block 768, 7 hours ago
|
|
|
|
I tried sending 10000 Tx out of my wallet and it made it freeze at block 91482, I went to check and repair my wallet and it comes up with a mismatch spent coins error:
23:04:32

checkwallet
23:04:32

{
"mismatched spent coins" : 1,
"amount in question" : 10000.00000000
}
23:04:58

repairwallet
23:04:58

{
"mismatched spent coins" : 1,
"amount affected by repair" : 10000.00000000
}
Not sure how to fix this issue, I have tried restarting the wallet, resyncing the wallet and everything else I can think of. Any ideas?
Does the repairwallet command not fix your issue? If not then I'll need to look into the function to see what could be going wrong. A workaround for this. If repairwallet is not working, is you could dump the private keys for your wallet to a text file, then re import them. Also could you tell me which client version and protocol version you are running? Open Debug console window and type resendtx. Sometimes it will resolve it. if not, restoring an earlier backup of your wallet should do the trick has for me in the past with other coins |
|
|
|
Maybe this ? ... or this  lmfao some people just don't take a hint or several and a no in this case |
|
|
|
|
Show Posts
