Topic: [ANN] 42 | Time to Revive 42 Coin - Everyone get in here!!! - page 12. (Read 357116 times)

do i smell a 42 revival??? heres hoping!! been running a private pool for awhile now and just went public!! (in hopes this would happen!) http://42.latenightminers.ca

so - can we agree on 4 years?

If so - I'm on board and lets work toward a fork.

In reference to HIppy Tech's question, I think it is the numerology which has attracted me to this coin.  I hate to see the number 42 itself sullied in reputation.  A planned reduction in reward to cap the supply at 42 as in my pull request is needed for the health of this integer. 

I'm the Dev now and as a miner and looking at other coins - rarely does any coin last for more than  few years so why try to keep the coin on life-support for 7 more years.

Plenty of coins do just fine after POW is over and the only reason I'm the Dev is because I offered to pay for a programmer to find a 'non existent' problem int eh code when cryptsy was worried there was a problem. I'll happily turns the reigns over to any other interested party, but I still like giving the coin just four more years in terms of POW life. The reason I offered to pay is because I just happen to like the coin and if you do remember - this coin hit 17 last summer.

let me know your opinions - thanks

Jeff at  Lifeforce Pools.

No. lol You are free to do as you please.

Lets just say I (and others) wouldn't be surprised if you turned out to be one of his alternate accounts.

lol i still remember dumping this for 1320

from 1600 to 4. i thought coin is dead)))

Good question, thank you!  
I offer not much time, and not much talent.  
But still having trouble answering your question

It looked completely abandoned.  Is there a do-not-resuscitate order?  

http://42.latenightminers.ca
New 42COIN pool open and out of beta

I smell a soopy-hendo !

Why the hell would anyone, with any coding talent, want to waste their time with this craptsy inhouse FAIL of a scamcoin ?

Thanks for taking a look and comments!

42coin Dev suggested only stretching it out over ~4 years.  I think this is makes more sense, the last few years in my previous proposal had 4 satoshi and 2 satoshi coinbase reward.  Kind of pointless  hopefully fees will be higher than that.  So I changed a few lines in the pull request.    

Yes fees will continue to support the network after that, good idea and the use them as an excuse for more 42 in the code!  Fees need certain minimums based on transaction size in kB to prevent DDOS, which are already in the code (for TX over 500 bytes).  Other than that there are no minimum tx fees based on amount of transaction.  I didn't mess with fees in this pull request which is just a coinbase reward fix, so, something to think about for the future or take a look yourself and submit a pull request.    

The only other thing here is I added a file Release.java which is just a simulator for adding up how many coins have been released.  

yay for the good work!

my 0.000042 worth of input:
go for fee only post 7 years (cold turkey rewards)
say 0.042% fixed fee

that makes 42 a store of value (but low transaction) COIN

if it is code able you could waive the fee for payments under 0.0001 [42s]
thus encourage micro payments and the big boys pay the toll.

Because there was such an overwhelmingly positive response to my suggestion I went ahead and issued a pull request to master branch at
github.com/fortytwo42/42.git

Please take a look at my suggested changes:
https://github.com/funkshelper/42/commit/66a64695862b6bf570b008e686b91a90e52a41a8


For review, as we stand right now we are going to see 42 total coins reached in about 250 days and then we will have more than 42 coins as the rewards keep coming.  So long and thanks for all the fish. 

With my suggested changes we push off the day of 42 coins to 7 years in the future.  The reward will slowly drop rather than go cold turkey and who knows, maybe some value will be added to coin in that time as more people are using public currencies.  It is more likely the network would survive.

 

 

great got an instant sync with those nodes!

[
{
"addr" : "182.19.198.161:24242",
"services" : "00000001",
"lastsend" : 1415633893,
"lastrecv" : 1415633904,
"conntime" : 1415631782,
"version" : 60001,
"subver" : "/42:0.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 467890,
"banscore" : 0
},
{
"addr" : "54.201.183.106:24242",
"services" : "00000001",
"lastsend" : 1415633893,
"lastrecv" : 1415633905,
"conntime" : 1415631788,
"version" : 60001,
"subver" : "/42:0.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 467891,
"banscore" : 0
},
{
"addr" : "71.175.81.45:24242",
"services" : "00000001",
"lastsend" : 1415633904,
"lastrecv" : 1415633917,
"conntime" : 1415631795,
"version" : 60001,
"subver" : "/42:0.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 467891,
"banscore" : 0
},
{
"addr" : "86.18.76.197:24242",
"services" : "00000001",
"lastsend" : 1415633893,
"lastrecv" : 1415633904,
"conntime" : 1415632325,
"version" : 60001,
"subver" : "/42:0.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 467904,
"banscore" : 0
},
{
"addr" : "72.78.100.13:24242",
"services" : "00000001",
"lastsend" : 1415633893,
"lastrecv" : 1415633904,
"conntime" : 1415632331,
"version" : 60001,
"subver" : "/42:0.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 467905,
"banscore" : 0
},
{
"addr" : "188.226.171.134:24242",
"services" : "00000001",
"lastsend" : 1415633893,
"lastrecv" : 1415633904,
"conntime" : 1415632576,
"version" : 60001,
"subver" : "/42:0.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 467909,
"banscore" : 0
},
{
"addr" : "76.125.230.79:24242",
"services" : "00000001",
"lastsend" : 1415633917,
"lastrecv" : 1415633871,
"conntime" : 1415633801,
"version" : 60001,
"subver" : "/42:0.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 467939,
"banscore" : 0
}
]

can someone do a getpeerinfo in a working wallet?
I have difficulties syncing my wallet

(used source from https://github.com/fourtytwo42/)

Here's an idea, please comment:

   if (nHeight >= 424242+42*42*42) {
        nSubsidy = 0.000024*COIN + fees;
   }


This by itself would reduce the reward, currently coming every 42 seconds at 0.000042   to 0.000024.  This will push back the day of reckoning quite a bit, specifically to block 1359421.  

It might seem tough for the miners now, not as bad as a halfing day but close,  but this sure seems better to me then just cutting them all off and saying goodbye to 42 coin once we have the 42 coins released in less than a year at block 990382.  Also better than just leaving constant reward as is and watching supply of 42coin go slowly up past 42.        

This change I recommend would come at block 498330, which will be about 21 days from now, that's when the fork would hit the network.  

Rumpey:  Blocks are humming along fine as far as I know.  I see 8 fully open nodes and close to a GHash of scrypt on the network.

Buckrogers: I know of no other wallets other than those available at github.com/fourtytwo42/42.

Hi, is there an actual working wallet that can be downloaded that has been verified to be safe and functional, if so, can someone please post the link for it here.

thanks!

So has the block chain started moving again, or is it frozen?

Hendo/maco/soopy ... also LTB?  scooby??

--
funkenstein marshall onward