Pages:
Author

Topic: [ANN] Techcoin [TECH] [186,985 PoW coins 4% PoS] [BITTREX] [ALLCOIN] - page 17. (Read 69898 times)

full member
Activity: 140
Merit: 100
Even with the new nodes - same story. Stuck at 5000.

I have uploaded the current blockchain to github for those having trouble getting synced:

https://github.com/techcoinproject/Techcoin/releases/tag/v1.0.1.1
hero member
Activity: 644
Merit: 500
TechCoin now trading on CoinCubess.
https://www.coincubess.com/trading/TECH_BTC
this is a scam site i think guys.becareful
newbie
Activity: 46
Merit: 0
Even with the new nodes - same story. Stuck at 5000.
sr. member
Activity: 392
Merit: 250
So much for "Community"
new nodes synced instantly.

now how to get coins in wallet.  hmm
full member
Activity: 140
Merit: 100
Thanks for the kind words Biomech - I do hope this coin can be rescued, it seems like it should be able to, one way or another.  We'll be working hard at it, that's for sure.  I've had my fingers in it since the mistake was discovered in 1.0.0.0 that had PoS starting at block 6000.  In case anyone is curious about this structured payout situation - HYP is in need of more regular staking, so rather than send the coins all at once I'm sending them in daily payments so his stake payouts will also be daily, and continuous.

So far we are trying the gentle approach here - now that the OP is updated we can get everyone running the current version, which may get enough weight on the network to get it moving on it's own.  I just had a thought that the nodes still running 1.0.0.0 may be the pools since they don't really care too much about PoS phase except to be able to let manual withdraws happen.  We're talking to the exchanges to get them updated before escalating.

The hard fork approach is waiting in the wings - we've coded what we think should re-start PoW at the current block, based on other coins that have had to do the same thing, tests ok - but pretty sure it needs to be fully deployed to start accepting new PoW blocks, no good way to test that out.  We'll deploy this after the update approach.

Hello DEVs

Thank you for your news on the progress of work. But I'm just an enthusiast and an investor, do not understand anything about the development of crypto-currencies or mining. So, could give an explanation for those who only purchase, hold or sell currencies?

What are the expectations of terms, values ​​and other details of marketing TECHCOIN?

Thank you and congratulations for the work.

Personally I'm concentrating on the technical aspects of saving this coin from the dustbin because I bought a bit, and since there are so few total coins, they should have gone WAY up in value instead of WAY down in value (since the original dev abandoned it to create new coins and leaving a huge mistake in the first version) and then I'll be thinking about what sort of future this coin has in the marketplace.  It would be nice to maybe get an online marketplace running where people can buy and sell high tech gear using TECH - put it right in the wallet or something.  Main goal right now is just to make the blockchain work properly, then we can have some fun.
full member
Activity: 140
Merit: 100
Is it safe to transfer coins to wallet now?  Trying to pick some up and help stake.

any nodes available? no connection/

addnode=24.85.126.229:57697
addnode=46.165.208.140:57697
addnode=198.199.123.234:48235

we really need to get all these old nodes updated, it's really messing with the network having so many 1.0.0.0 nodes running still, they could even be preventing PoS blocks because that old wallet version won't accept PoS blocks until 6000.


Code:
"addr" : "108.163.232.221:57697",
"services" : "00000001",
"lastsend" : 1406005093,
"lastrecv" : 1406005093,
"conntime" : 1405841139,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 5000,
"banscore" : 0
},
{
"addr" : "46.105.118.15:57697",
"services" : "00000001",
"lastsend" : 1406003773,
"lastrecv" : 1406003773,
"conntime" : 1405841256,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 5000,
"banscore" : 0
},
{
"addr" : "198.100.154.180:57697",
"services" : "00000001",
"lastsend" : 1406003513,
"lastrecv" : 1406003513,
"conntime" : 1405841350,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 5000,
"banscore" : 0
},
{
"addr" : "162.243.206.226:57697",
"services" : "00000001",
"lastsend" : 1406004905,
"lastrecv" : 1406004906,
"conntime" : 1405844871,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 5000,
"banscore" : 0
},
{
"addr" : "86.135.29.63:57697",
"services" : "00000001",
"lastsend" : 1406004374,
"lastrecv" : 1406004374,
"conntime" : 1405936747,
"version" : 60013,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"startingheight" : 5062,
"banscore" : 0
},
{
"addr" : "192.99.36.115:47432",
"services" : "00000001",
"lastsend" : 1406005064,
"lastrecv" : 1406005064,
"conntime" : 1405963912,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 5000,
"banscore" : 0
},
{
"addr" : "46.165.208.140:57697",
"services" : "00000001",
"lastsend" : 1406003475,
"lastrecv" : 1406003475,
"conntime" : 1405967352,
"version" : 60013,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"startingheight" : 5068,
"banscore" : 0
},
{
"addr" : "198.199.123.234:48235",
"services" : "00000001",
"lastsend" : 1406003915,
"lastrecv" : 1406003915,
"conntime" : 1405975027,
"version" : 60013,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : true,
"startingheight" : 5068,
"banscore" : 0
},
{
"addr" : "67.215.11.195:55764",
"services" : "00000001",
"lastsend" : 1406005043,
"lastrecv" : 1406005043,
"conntime" : 1405975101,
"version" : 60013,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : true,
"startingheight" : 5062,
"banscore" : 0
},
{
"addr" : "73.55.246.45:46286",
"services" : "00000001",
"lastsend" : 1406005049,
"lastrecv" : 1406005049,
"conntime" : 1405975319,
"version" : 60013,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"startingheight" : 5062,
"banscore" : 0
},
{
"addr" : "98.234.71.71:51186",
"services" : "00000001",
"lastsend" : 1406005047,
"lastrecv" : 1406005047,
"conntime" : 1405975398,
"version" : 60013,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"startingheight" : 5062,
"banscore" : 0
},
{
"addr" : "86.92.170.206:59354",
"services" : "00000001",
"lastsend" : 1406004651,
"lastrecv" : 1406004651,
"conntime" : 1405975645,
"version" : 60013,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"startingheight" : 5062,
"banscore" : 0
},
{
"addr" : "192.99.47.133:46613",
"services" : "00000001",
"lastsend" : 1406005041,
"lastrecv" : 1406005041,
"conntime" : 1405975781,
"version" : 60013,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"startingheight" : 5000,
"banscore" : 0
},
{
"addr" : "81.21.242.38:53644",
"services" : "00000001",
"lastsend" : 1406004612,
"lastrecv" : 1406004612,
"conntime" : 1405978261,
"version" : 60013,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"startingheight" : 5067,
"banscore" : 0
},
{
"addr" : "124.121.101.77:55045",
"services" : "00000001",
"lastsend" : 1406003657,
"lastrecv" : 1406003657,
"conntime" : 1405983236,
"version" : 60013,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"startingheight" : 5062,
"banscore" : 0
},
{
"addr" : "80.1.123.250:49314",
"services" : "00000001",
"lastsend" : 1406003741,
"lastrecv" : 1406003739,
"conntime" : 1406003738,
"version" : 60013,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : true,
"startingheight" : 5065,
"banscore" : 0
},
{
"addr" : "137.135.57.55:1312",
"services" : "00000001",
"lastsend" : 1406004462,
"lastrecv" : 1406004459,
"conntime" : 1406004458,
"version" : 60013,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : true,
"startingheight" : 5062,
"banscore" : 0
},
{
"addr" : "93.155.146.79:58622",
"services" : "00000001",
"lastsend" : 1406004703,
"lastrecv" : 1406004700,
"conntime" : 1406004699,
"version" : 60013,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : true,
"startingheight" : 5001,
"banscore" : 0
full member
Activity: 140
Merit: 100
Hello, my wallet is stuck at block 5001/5062. Running the latest version, deleted all but wallet.dat before instalation.

We're looking at adding a checkpoint to a minor update to help initial syncing.  Best chance is to either close and re-open the wallet until it syncs or just leave it running until it decides to sync with the most up to date blockchain.  I'll get a fresh addnode list together.
full member
Activity: 140
Merit: 100
Is it safe to transfer coins to wallet now?  Trying to pick some up and help stake.

The blockchain is not moving right now, so wait until it's moving again.
sr. member
Activity: 392
Merit: 250
So much for "Community"
Is it safe to transfer coins to wallet now?  Trying to pick some up and help stake.

any nodes available? no connection/
sr. member
Activity: 392
Merit: 250
So much for "Community"
Is it safe to transfer coins to wallet now?  Trying to pick some up and help stake.
newbie
Activity: 46
Merit: 0
Hello, my wallet is stuck at block 5001/5062. Running the latest version, deleted all but wallet.dat before instalation.
full member
Activity: 165
Merit: 100
Thanks for the kind words Biomech - I do hope this coin can be rescued, it seems like it should be able to, one way or another.  We'll be working hard at it, that's for sure.  I've had my fingers in it since the mistake was discovered in 1.0.0.0 that had PoS starting at block 6000.  In case anyone is curious about this structured payout situation - HYP is in need of more regular staking, so rather than send the coins all at once I'm sending them in daily payments so his stake payouts will also be daily, and continuous.

So far we are trying the gentle approach here - now that the OP is updated we can get everyone running the current version, which may get enough weight on the network to get it moving on it's own.  I just had a thought that the nodes still running 1.0.0.0 may be the pools since they don't really care too much about PoS phase except to be able to let manual withdraws happen.  We're talking to the exchanges to get them updated before escalating.

The hard fork approach is waiting in the wings - we've coded what we think should re-start PoW at the current block, based on other coins that have had to do the same thing, tests ok - but pretty sure it needs to be fully deployed to start accepting new PoW blocks, no good way to test that out.  We'll deploy this after the update approach.

Hello DEVs

Thank you for your news on the progress of work. But I'm just an enthusiast and an investor, do not understand anything about the development of crypto-currencies or mining. So, could give an explanation for those who only purchase, hold or sell currencies?

What are the expectations of terms, values ​​and other details of marketing TECHCOIN?

Thank you and congratulations for the work.
full member
Activity: 140
Merit: 100
Thanks for the kind words Biomech - I do hope this coin can be rescued, it seems like it should be able to, one way or another.  We'll be working hard at it, that's for sure.  I've had my fingers in it since the mistake was discovered in 1.0.0.0 that had PoS starting at block 6000.  In case anyone is curious about this structured payout situation - HYP is in need of more regular staking, so rather than send the coins all at once I'm sending them in daily payments so his stake payouts will also be daily, and continuous.

So far we are trying the gentle approach here - now that the OP is updated we can get everyone running the current version, which may get enough weight on the network to get it moving on it's own.  I just had a thought that the nodes still running 1.0.0.0 may be the pools since they don't really care too much about PoS phase except to be able to let manual withdraws happen.  We're talking to the exchanges to get them updated before escalating.

The hard fork approach is waiting in the wings - we've coded what we think should re-start PoW at the current block, based on other coins that have had to do the same thing, tests ok - but pretty sure it needs to be fully deployed to start accepting new PoW blocks, no good way to test that out.  We'll deploy this after the update approach.
legendary
Activity: 1372
Merit: 1022
Anarchy is not chaos.
FWIW:

Up till a few days ago, my interaction with the new dev had only been a few comments back and forth, and he always seemed quite intelligent. As of 6 days prior, we made a trade, the details of which I won't reveal without his consent except to say that on his side it was a structured payout.

To date he has been completely diligent in this deal, and we have talked quite a bit about the future of several coins. I found out about this one through  him. I'm not invested, but I do believe y'all have found a good man to steer the ship. Best of luck, ladies and gentlemen. I'm watching for now. Might invest in the future, but everything I have is tied up right now.
newbie
Activity: 48
Merit: 0
I have used the 1.0.1.1 version from 1st July.
newbie
Activity: 52
Merit: 0
Is there an active dev on this project?  Is there a working blockchain explorer?

Blocks have been really slow and I can't tell if its us or the network.

Thanks,
richie@bittrex

No, this one is abandoned by Carsen, Richie...

https://bitcointalksearch.org/topic/m.7929678

I chatted with Carsen - he admits to moving on and has agreed to hand over the thread to me and work with us to fix the coin.  I am now the operator of the techcoinproject user so I'll be updating the OP finally.  I have not paid anything or received anything, this is purely for the good of the coin and our collective investments in it, especially those of us who bought in for the long term gains and WANT to stake.  I think IF everyone updates to the latest wallet we might be able to avoid another hard fork and PoW...  let's get rolling!


Thank you for the block explorer.. super helpful..  Currently we are stuck on 5062.  

  "version" : "v1.0.0.1",
    "protocolversion" : 60013,
    "walletversion" : 60000,
    "blocks" : 5062,

please let us know when there is an updated wallet ... email support at bittrex.com

Thanks,
richie@bittrex

OP updated.  1.0.0.1 will get stuck at 5062 because stake at 5063 relied on the changes in 1.0.1.1

The source code was updated on july 1st, so if you built that wallet on june 29th when 1.0.0.1 came out, it's out of date.  I'll see about getting a copy of the blockchain uploaded somewhere in case there's a problem getting to block 5068 by sync.
hero member
Activity: 937
Merit: 1000
Is there an active dev on this project?  Is there a working blockchain explorer?

Blocks have been really slow and I can't tell if its us or the network.

Thanks,
richie@bittrex

No, this one is abandoned by Carsen, Richie...

https://bitcointalksearch.org/topic/m.7929678

I chatted with Carsen - he admits to moving on and has agreed to hand over the thread to me and work with us to fix the coin.  I am now the operator of the techcoinproject user so I'll be updating the OP finally.  I have not paid anything or received anything, this is purely for the good of the coin and our collective investments in it, especially those of us who bought in for the long term gains and WANT to stake.  I think IF everyone updates to the latest wallet we might be able to avoid another hard fork and PoW...  let's get rolling!


Thank you for the block explorer.. super helpful..  Currently we are stuck on 5062. 

  "version" : "v1.0.0.1",
    "protocolversion" : 60013,
    "walletversion" : 60000,
    "blocks" : 5062,

please let us know when there is an updated wallet ... email support at bittrex.com

Thanks,
richie@bittrex
full member
Activity: 140
Merit: 100
Is there an active dev on this project?  Is there a working blockchain explorer?

Blocks have been really slow and I can't tell if its us or the network.

Thanks,
richie@bittrex

No, this one is abandoned by Carsen, Richie...

https://bitcointalksearch.org/topic/m.7929678

I chatted with Carsen - he admits to moving on and has agreed to hand over the thread to me and work with us to fix the coin.  I am now the operator of the techcoinproject user so I'll be updating the OP finally.  I have not paid anything or received anything, this is purely for the good of the coin and our collective investments in it, especially those of us who bought in for the long term gains and WANT to stake.  I think IF everyone updates to the latest wallet we might be able to avoid another hard fork and PoW...  let's get rolling!
full member
Activity: 140
Merit: 100
Is there an active dev on this project?  Is there a working blockchain explorer?

Blocks have been really slow and I can't tell if its us or the network.

Thanks,
richie@bittrex

It is the network, basically it has run out of PoS blocks and new weight is not coming online fast enough, so no new blocks for days.

Do you disable staking with your wallets to minimize CPU usage?   It would help move the blockchain if it could be enabled, at least temporarily.

I am working with ceceilbdemented to code changes and compile a new version of the wallet that should allow a PoW restart until block 6000, and with luck it should happen with fees as the only reward so we won't produce more base currency than was originally created.

We're testing the changes now but I think a PoW block won't actually be accepted until the majority of the network updates to the new code, so we might not know if the changes were successful until fully deployed...  We'll start a new thread since the original dev has moved on to his lastest proof of scam coin and abandoned this one like all his others.  My Abe hack block explorer at http://techblocks.chainworks.info:8324/chain/Techcoin is up to date, but the chain is stuck.
legendary
Activity: 2688
Merit: 1240
Is there an active dev on this project?  Is there a working blockchain explorer?

Blocks have been really slow and I can't tell if its us or the network.

Thanks,
richie@bittrex

No, this one is abandoned by Carsen, Richie...

https://bitcointalksearch.org/topic/m.7929678
Pages:
Jump to: