|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
|
|
|
|
|
|
|
|
Lasergun
|
 |
June 07, 2016, 10:00:51 AM |
|
Since hendo420 closed the original topic and lost somewhere in the past, I decide to open a new thread to bring the 42 back to the future.  |
|
|
|
|
|
vividly
|
|
June 07, 2016, 10:13:19 AM |
|
I like your project. I will be following it!
|
|
|
|
|
|
axxo
|
|
June 07, 2016, 10:19:26 AM |
|
I thought hendo420 was trying to revive this coin late last year, what happened then?
|
|
|
|
|
|
Lasergun
|
|
June 07, 2016, 10:24:08 AM |
|
I thought hendo420 was trying to revive this coin late last year, what happened then?
I contacted him two weeks ago regarding this matter, his answer was: " I tried to revive the coin but was trolled pretty bad so decided not to do a revival." |
|
|
|
|
|
jwiz168
|
|
June 07, 2016, 10:26:33 AM |
|
Is this a re-issue of the 42 coins way back in 2013?
|
|
|
|
|
Lasergun
|
|
June 07, 2016, 11:04:41 AM |
|
Is this a re-issue of the 42 coins way back in 2013?
Yes, it is. The genesis block was created on 7th Jan 2014 01:09:14. But I plan to make a new client on modern codebase and migrate to it due to the large number of issues with the original codebase. |
|
|
|
|
|
docker
|
|
June 07, 2016, 11:11:36 AM |
|
Is this a re-issue of the 42 coins way back in 2013?
Yes, it is. The genesis block was created on 7th Jan 2014 01:09:14. But I plan to make a new client on modern codebase and migrate to it due to the large number of issues with the original codebase. So we can use our old 42 coins or everything will be new? |
|
|
|
|
|
Lasergun
|
|
June 07, 2016, 11:32:01 AM |
|
So we can use our old 42 coins or everything will be new?
Actually, all depends of the community and desirable changes. I propose redemption (swap), during which old 42-s will be redeemable for new 42-s on a 1:1 basis, old 42-s will be destroyed at the same time. |
|
|
|
|
Woody20285
Legendary
 Offline
Activity: 868
XDE2, PAYS HUNDREDS OF DOLLARS A WEEK TO PROMOTERS
|
|
June 07, 2016, 04:17:13 PM |
|
Hey Lasergun - Thank you for picking this up - look forward to
your leadership.
|
|
|
|
|
Edkemper
|
|
June 07, 2016, 04:19:56 PM |
|
Wasn't 42 coin one of the most expensive coin ever made so far, about 2 to 3 years ago?
|
|
|
|
|
Lasergun
|
|
June 07, 2016, 07:00:56 PM |
|
Wasn't 42 coin one of the most expensive coin ever made so far, about 2 to 3 years ago?
You are right, 42 was the most expensive coin ever made, at its peak value in 2014, 42 was traded at the highest rate at 1900.00 btc:  and the current price is 0.0654 btc, I made a screenshot for the future reference:  |
|
|
|
|
|
funkenstein
|
|
June 07, 2016, 10:08:58 PM |
|
Cool. Wishing y'all good luck! You might want to check my post on 42coin from last year. http://frass.woodcoin.org/the-42coin-saga/There's also this one: https://github.com/funkshelper/42-limited-editionAll it would take would be for a couple of you to start mining using that one and hey presto - a limited supply coin. Kind of antisocial to recommend forking from a year old point but hey - altcoins are about experimentation aren't they?  Not that scrypt coin on its own could tread water today.. move algos? switch to mergemined like doge? |
"Give me control over a coin's checkpoints and I care not who mines its blocks." http://vtscc.org |
|
|
|
docker
|
|
June 07, 2016, 10:16:54 PM |
|
So we can use our old 42 coins or everything will be new?
Actually, all depends of the community and desirable changes. I propose redemption (swap), during which old 42-s will be redeemable for new 42-s on a 1:1 basis, old 42-s will be destroyed at the same time. Thanks for the quick answer mate good luck |
|
|
|
|
|
Lasergun
|
|
June 07, 2016, 10:55:50 PM |
|
Thank you for the support, guys!
The first priority now is to choose the emission model, so don't forget to submit your vote.
|
|
|
|
|
|
M8BWNNRFMNdak68c
|
|
June 08, 2016, 04:55:44 AM |
|
i tried the last version ( https://github.com/fourtytwo42/42 ) several times last year.. i was never able to fetch up the the highest blocks.. the chain always got stuck.. i also heard there were different chains.. hendo wanted to fix that, but actually did nothing.. it also consumes a lot of cpu and reacts very slow.. so what are you going to do against that? here my actual getinfo, what are your numbers? {
"version" : 70000,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 990381,
"connections" : 2,
"proxy" : "",
"difficulty" : 6.54806459,
"testnet" : false,
"keypoololdest" : 1450018601,
"keypoolsize" : 101,
"paytxfee" : 0.00000001,
"mininput" : 0.00000001,
"errors" : "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}
here some random output: ERROR: FetchInputs() : 97071ce3a3 mempool Tx prev not found b28ca71d1b
ignoring large orphan tx (size: 35427, hash: 97071ce3a3)
ERROR: FetchInputs() : ad6070b410 mempool Tx prev not found 02531a55cf
ignoring large orphan tx (size: 64619, hash: ad6070b410)
ERROR: FetchInputs() : 3ebf809fd8 mempool Tx prev not found d5764cff71
ignoring large orphan tx (size: 41975, hash: 3ebf809fd8)
ERROR: FetchInputs() : d8d88a5666 mempool Tx prev not found cfa29d5e2e
ignoring large orphan tx (size: 40913, hash: d8d88a5666)
ERROR: FetchInputs() : fbb9fc6b30 mempool Tx prev not found 1cc54df938
ignoring large orphan tx (size: 51720, hash: fbb9fc6b30)
connection timeout
trying connection 82.192.198.114:24242 lastseen=0.9hrs
connect() failed after select(): Connection refused
trying connection 88.206.187.1:24242 lastseen=0.9hrs
connection timeout
trying connection 82.29.4.122:24242 lastseen=0.9hrs
received block 8a0db20952f8fc9dfa43
ProcessBlock: ORPHAN BLOCK, prev=537d02746a18232b4929
connection timeout
trying connection 82.29.4.122:24242 lastseen=0.9hrs
connection timeout
trying connection 73.211.90.130:24242 lastseen=0.9hrs
|
|
|
|
|
|
Lasergun
|
|
June 08, 2016, 08:21:21 AM |
|
i tried the last version ( https://github.com/fourtytwo42/42 ) several times last year.. i was never able to fetch up the the highest blocks.. the chain always got stuck.. i also heard there were different chains.. hendo wanted to fix that, but actually did nothing.. it also consumes a lot of cpu and reacts very slow.. so what are you going to do against that? here my actual getinfo, what are your numbers? {
"version" : 70000,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 1636180,
"connections" : 5,
"proxy" : "",
"difficulty" : 3.72573365,
"testnet" : false,
"keypoololdest" : 1452611907,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"mininput" : 0.00000001,
"errors" : ""
} This is a well known problem with all 42 clients (included the latest v. 8.0.0, compiled by soopy452000). It is appear when your client established connections with clients from alien chains ("subver" : Satoshi:0.6.3, Satoshi:0.8.5, DigitalcoinV3.0:3.0.1, WorldcoinFoundation:0.8.6.2...), you can avoid such problem by blocking their ports (9538, 9556, 9065, 9336, 9333, 7999, 11081, 28753, 9526, 19904, 9771). Will be fixed in client on a new codebase. |
|
|
|
|
|
tolikkk
|
|
June 08, 2016, 12:56:41 PM |
|
I think, we need to leave only 42 coins to start intense marketing campaign to enhance the status of the coins and to attract potential investors and to coin continued to live
|
|
|
|
|
|
|
|
Poll
