Wow stake weight has dropped like a stone since the halving! My estimated time is now under an hour from previously 5-6 hours. Are loads of people selling instead of staking suddenly?
Still no sync, this is why I do not buy more, wallet unstable
Topic: [ANN] 1337 [MANDATORY UPDATE] 41.78% APR| POS ONLY - page 109. (Read 259518 times)
Still no sync, this is why I do not buy more, wallet unstable
Wow stake weight has dropped like a stone since the halving! My estimated time is now under an hour from previously 5-6 hours. Are loads of people selling instead of staking suddenly?
2 days for the halving and the price on the alternative markets is going up 
Hey mate,
What is the halving going to be? as I can't seem to find anything about it on here.Maybe I missed it going through the pages but I can't seem to find anything about a halving.
I am still buying as much 1337 coins from the satoshi's I earn from faucets. I'm now even earning Litoshi which I'm also going to use and buy 1337 coins. I am currently doing this to buy a few Altcoins as it's a great way to build my stack and the best thing is that it's for free and before people say you spend a lot of time claiming, well I don't as I just claim every 30 minutes or so which still adds up fast.
Quote from: malyan on November 19, 2016, 01:21:31 PM
Now, what percentage of the POS?
'now' its still 334.25% but starting november 25th it will be 1337/8= 167.125%
i also keep buying 1337 from faucets and trading earnings
Thanks mate for posting this, as I said I must of missed it lol
Glad to hear I'm not the only one buying 1337 coins from faucets and it's a great day for newbies to get in for little or no investment.
2 days for the halving and the price on the alternative markets is going up
Hey mate,
What is the halving going to be? as I can't seem to find anything about it on here.Maybe I missed it going through the pages but I can't seem to find anything about a halving.
I am still buying as much 1337 coins from the satoshi's I earn from faucets. I'm now even earning Litoshi which I'm also going to use and buy 1337 coins. I am currently doing this to buy a few Altcoins as it's a great way to build my stack and the best thing is that it's for free and before people say you spend a lot of time claiming, well I don't as I just claim every 30 minutes or so which still adds up fast.
Quote from: malyan on November 19, 2016, 01:21:31 PM
Now, what percentage of the POS?
'now' its still 334.25% but starting november 25th it will be 1337/8= 167.125%
i also keep buying 1337 from faucets and trading earnings
2 days for the halving and the price on the alternative markets is going up
Hey mate,
What is the halving going to be? as I can't seem to find anything about it on here.Maybe I missed it going through the pages but I can't seem to find anything about a halving.
I am still buying as much 1337 coins from the satoshi's I earn from faucets. I'm now even earning Litoshi which I'm also going to use and buy 1337 coins. I am currently doing this to buy a few Altcoins as it's a great way to build my stack and the best thing is that it's for free and before people say you spend a lot of time claiming, well I don't as I just claim every 30 minutes or so which still adds up fast.
The wallet v1.6.0.1-g fell down suddenly without connection, I opened the wallet v1.5.04-g and it works.
Because?
Because?
Just My Idea
to make Thread STAKE4COFFEE ( S4C )
just Stake 1337 coin and Get coffee.
MayBe Just for me.
stiil waiting for swap..
to make Thread STAKE4COFFEE ( S4C )
just Stake 1337 coin and Get coffee.
MayBe Just for me.
stiil waiting for swap..
2 days for the halving and the price on the alternative markets is going up
I'll setup 1337 tommorow on another server and see if it has same problems...
is this coin still alive? last time I see people dump at 1 satoshi and no one buying....
and now people are dumping the coin for 0.3 satoshi, and still i think it worth buying the coin. because:
halving, burning coins and swap.
also bitcoin price is up so it always make altcoin price down.
Kiklo's Premium Blockchain Snapshot Service
1337 Snapshot updated to 11-20-2016
https://bitcointalksearch.org/topic/m.15734992
1337 Snapshot updated to 11-20-2016
https://bitcointalksearch.org/topic/m.15734992
is this coin still alive? last time I see people dump at 1 satoshi and no one buying....
1337 stayed at 2 buy and 1 sell for many months and was profitable even though you bought at a 50% loss because 100% took less then a month. So one month and you in profits. Remember you buying for 2 but only selling for 1 . Eventualy thing came to an end and people started selling for 1 more often then before . So the buy order was filled up then it just drained and now we looking at 1337 being less than 1 satoshi since we can only trade it for altcoins. Even the altcoin to 1337 coin trade is terrible. Its dying there to that's if you ever considered it born there to begin with.
is this coin still alive? last time I see people dump at 1 satoshi and no one buying....
Which Block explorer is on the right wallet version & block height and I will sync my snapshot of 1337.
http://www.presstab.pw/phpexplorer/1337/index.php
TIA
"version" : "v1.6.0.1-g",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 589190,
"timeoffset" : -1,
"connections" : 84,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 125.76997466
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
just as a FYI, my node is fully synched without any errors as you can see.
and FYI i never said is node problem, but coin code problem"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 589190,
"timeoffset" : -1,
"connections" : 84,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 125.76997466
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
just as a FYI, my node is fully synched without any errors as you can see.
1.6.0.1?
yeah disregard the version number. i was a bit too lazy to change it on my vps but the rest is the same as in 1.6.0.2
look, when i took over the coin everything was working fine. after BanzaiBTC helped me with adding some new features to it, it started to fork on ccex (but only ccex). it became obvious that this was caused because ccex was staking their users coins so i assumed that caused the problems on their end.
after that i hired presstab to add the multi-send feature and asked him to take a look at the code. both devs are good at what they do IMHO. otherwise i wouldnt have hired them.
im thinking of releasing a 'plain' wallet without the extra features in it because this sucks for both the users as for me.
Which Block explorer is on the right wallet version & block height and I will sync my snapshot of 1337.
"version" : "v1.6.0.1-g",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 589190,
"timeoffset" : -1,
"connections" : 84,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 125.76997466
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
just as a FYI, my node is fully synched without any errors as you can see.
and FYI i never said is node problem, but coin code problem"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 589190,
"timeoffset" : -1,
"connections" : 84,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 125.76997466
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
just as a FYI, my node is fully synched without any errors as you can see.
1.6.0.1?
"version" : "v1.6.0.1-g",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 589190,
"timeoffset" : -1,
"connections" : 84,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 125.76997466
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
just as a FYI, my node is fully synched without any errors as you can see.
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 589190,
"timeoffset" : -1,
"connections" : 84,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 125.76997466
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
just as a FYI, my node is fully synched without any errors as you can see.
stuck on same block on both windows and linux
prolly you've been fed with dirty data and stuck in a fork - use kiklo's chain snapshot, and resync.
there's no reason to wait for hours, this coin is safe enough, it won't perform long rollbacks
same goes to the guy with negative calculated stake,
usually that means it's been fed with a block from the wrong chain
which has timestamp less than previous block on the right chain,
time delta becomes negative and so is the calculated stake
then check your ssd/hdd, timeoffset, connnections (should be >10 if listen=1) and coffee machine,
and of course syncing should be done in locked state,
if nothing helps - try syncing with empty wallet.dat and a pair of jamaican cigars
stuck on same block on both windows and linux
prolly you've been fed with dirty data and stuck in a fork - use kiklo's chain snapshot, and resync.
there's no reason to wait for hours, this coin is safe enough, it won't perform long rollbacks
same goes to the guy with negative calculated stake,
usually that means it's been fed with a block from the wrong chain
which has timestamp less than previous block on the right chain,
time delta becomes negative and so is the calculated stake
Jump to: