Bitcoin Forum
May 15, 2021, 03:52:55 PM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: no poll currently
yes - 41 (69.5%)
no - 18 (30.5%)
Total Voters: 59

Pages: « 1 ... 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 [230] 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 ... 323 »
  Print  
Author Topic: [ANN][LEAF] LEAFCOIN - Android wallet launched  (Read 352279 times)
damnation
Member
**
Offline Offline

Activity: 98
Merit: 10

https://bitcointalk.org/index.php?topic=434996.0


View Profile WWW
February 07, 2014, 11:25:47 AM
 #4581

mcg so next retarget means thgat we will mine 15,8x more? Wink
And after next 240blocks what diff will we have?
Meaby a good idea wuold be to make retarget more often than 240 blocks, can it be changed?

thats pretty much why we are having the new wallet.. the gravity well will retarget diff at every block.. so if multipool leaves.. it will drop down to what the current network hash rate is immediately.

♔ PrimeDice : The Premier Bitcoin Gambling Experience @PrimeDice
Noble:9ZQo8HaeCjporC7T4PFgVcqzXc5KLyGrnV
LOT: LzUoeyakB8DRoHgqMgHSWMzipW5Nr63zkg
BTC: 1EiY4FqGbbfL6VUhiVLe8Z5R7BVVyyLTmw
LTC: LaGJ2utSYG4bhQ882mJ8QkS1bq45p25vcD
1621093975
Hero Member
*
Offline Offline

Posts: 1621093975

View Profile Personal Message (Offline)

Ignore
1621093975
Reply with quote  #2

1621093975
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1621093975
Hero Member
*
Offline Offline

Posts: 1621093975

View Profile Personal Message (Offline)

Ignore
1621093975
Reply with quote  #2

1621093975
Report to moderator
1621093975
Hero Member
*
Offline Offline

Posts: 1621093975

View Profile Personal Message (Offline)

Ignore
1621093975
Reply with quote  #2

1621093975
Report to moderator
mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 11:28:07 AM
 #4582

mcg so next retarget means thgat we will mine 15,8x more? Wink
And after next 240blocks what diff will we have?
Meaby a good idea wuold be to make retarget more often than 240 blocks, can it be changed?

sure i could change it... but we need to push out another update then.

i would also change the kgw block to 19800 if i could pushout a new update.

i think pushing out a new update is a bit pushing our luck.

i would need to contact everyone again etc....

lets just hope the pool keeps it word and lessens the ghash targetted at us..

so we can reach the block more quickly

also, only 32% has upgraded.

ppl need to upgrade.
mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 11:29:48 AM
 #4583

I can't update with the mega link... What am I supposed to do with the github one ?

what do you mean? can you provide me more detail? does the link not work ie?
mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 11:33:21 AM
 #4584

cryptsy down again...
damnation
Member
**
Offline Offline

Activity: 98
Merit: 10

https://bitcointalk.org/index.php?topic=434996.0


View Profile WWW
February 07, 2014, 11:35:57 AM
 #4585

cryptsy down again...

been down for a little over an hour i think...

♔ PrimeDice : The Premier Bitcoin Gambling Experience @PrimeDice
Noble:9ZQo8HaeCjporC7T4PFgVcqzXc5KLyGrnV
LOT: LzUoeyakB8DRoHgqMgHSWMzipW5Nr63zkg
BTC: 1EiY4FqGbbfL6VUhiVLe8Z5R7BVVyyLTmw
LTC: LaGJ2utSYG4bhQ882mJ8QkS1bq45p25vcD
stevenb
Sr. Member
****
Offline Offline

Activity: 490
Merit: 250


View Profile
February 07, 2014, 11:43:34 AM
 #4586

I think we should implement Kimoto Gravity as fast as possible. Block 21203 is too far away, why need to wait almost 3200 blocks for an emergency fix? If Multipool jump in before block 21203 and make the diff skyhigh again, then Leafcoin will be definitely dead because no one want to mine at high diff. Currently nethash only 0.6 Ghs at block 17988.

mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 11:45:45 AM
 #4587

so do another update round? ppl dont upgrade.... we have to give time for them to update. Also i want to see what happens now...
luke997
Full Member
***
Offline Offline

Activity: 252
Merit: 100


View Profile
February 07, 2014, 11:48:33 AM
 #4588

I think we should implement Kimoto Gravity as fast as possible. Block 21203 is too far away, why need to wait almost 3200 blocks for an emergency fix? If Multipool jump in before block 21203 and make the diff skyhigh again, then Leafcoin will be definitely dead because no one want to mine at high diff. Currently nethash only 0.6 Ghs at block 17988.

I agree, this time we should anticipate diff swing and target more agressively, diff is going to jump to very high with such low current value.
The more swing cycle the worse they get.

Let's rollout real soon and nag people eveywhere to update....
Ziploc
Sr. Member
****
Offline Offline

Activity: 407
Merit: 250


View Profile
February 07, 2014, 11:49:10 AM
 #4589

would you be able to push a network message to all wallets ?
mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 11:50:23 AM
 #4590

would you be able to push a network message to all wallets ?

havent done it before... need to look.

so i will put the foundation on hold and do once more an update

give me a blocknumber

we will wait to see what happens in 3 hours ( pool agreement ).

if its not satisfying.. we will push out one more time.

agreed?

and i will look into the network push message.


C3ALL
Full Member
***
Offline Offline

Activity: 140
Merit: 100


★ BitClave ICO: 08/11/17 ★


View Profile
February 07, 2014, 11:52:08 AM
 #4591

Cant roll out another update before people have even done this one.  It will just get confusing with the number of updates being pushed out, some exchanges may even get sick of all the updates and drop the coin.

There will be a period of time when the diff swings slow the coin for a while, but long term it will resolve the issues.  So, people taking the short term view may get burned, people taking the long term view may see rewards.  Thats my opinion, but just as long as there remains enough support to pull this through the next high diff after the next multipool jump in.

People can see when gravity is coming, so as long as there are enough people keeping a bit of hash rate pointed at the coin, all will work out eventually.  Pushing out too many updates has just as much pottential to kill a coin as the multipools.

stevenb
Sr. Member
****
Offline Offline

Activity: 490
Merit: 250


View Profile
February 07, 2014, 11:54:47 AM
 #4592

would you be able to push a network message to all wallets ?

havent done it before... need to look.

so i will put the foundation on hold and do once more an update

give me a blocknumber

but we will wait to see what happens in 3 hours.

if its not satisfying.. we will push out one more time.

agreed?

and i will look into the network push message.



Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

C3ALL
Full Member
***
Offline Offline

Activity: 140
Merit: 100


★ BitClave ICO: 08/11/17 ★


View Profile
February 07, 2014, 12:06:14 PM
 #4593


Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

Even if middlecoin doesnt join in, the other locusts will.  As soon as we hit block 18,000 when the multipools join back in, it could hit 18,240 within 40 minutes.   Last time the multipools joined in at a low diff (and it wasnt even this low) there was a block every 10 seconds.  This time it could be even quicker.   No way at all to get an update out before 18240 it would fork for sure.

mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 12:09:47 PM
 #4594

would you be able to push a network message to all wallets ?

havent done it before... need to look.

so i will put the foundation on hold and do once more an update

give me a blocknumber

but we will wait to see what happens in 3 hours.

if its not satisfying.. we will push out one more time.

agreed?

and i will look into the network push message.



Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

i looked into the upgrade message.  its only shown when an invalid chain is found ( invalid proof of work )

printf("InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.\n");

so its kinda automatic @ block 21203... i couldnt find a way to push a message out. only thing i can do is provide future support on this. but then again... another update would be needed ( but that doesnt affect clients on current grav-2 version.. its just a program update.. no proofofwork/diff update ).

setting it at 18240 is WAY too risky... we have a very good chance of a fork. thats more ugly then just wait for kgw to kick in.

everyone has to update.. setting it at that block... would give them merely a day.

also take the weekend into account.

i dont think we should do that.

we have chosen block 21203 for a reason... allowing 7-10 days to upgrade.

if we make a change... it would have to be at least block 20k

luke997
Full Member
***
Offline Offline

Activity: 252
Merit: 100


View Profile
February 07, 2014, 12:14:50 PM
 #4595

would you be able to push a network message to all wallets ?

havent done it before... need to look.

so i will put the foundation on hold and do once more an update

give me a blocknumber

but we will wait to see what happens in 3 hours.

if its not satisfying.. we will push out one more time.

agreed?

and i will look into the network push message.



Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

i looked into the upgrade message.  its only shown when an invalid chain is found ( invalid proof of work )

printf("InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.\n");

so its kinda automatic @ block 21203... i couldnt find a way to push a message out. only thing i can do is provide future support on this. but then again... another update would be needed.

setting it at 18240 is WAY too risky... we have a very good chance of a fork. thats more ugly then just wait for kgw to kick in.

everyone has to update.. setting it at that block... would give them merely a day.

i dont think we should do that.

we have chosen block 21203 for a reason... allowing 7-10 days to upgrade.





Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

Even if middlecoin doesnt join in, the other locusts will.  As soon as we hit block 18,000 when the multipools join back in, it could hit 18,240 within 40 minutes.   Last time the multipools joined in at a low diff (and it wasnt even this low) there was a block every 10 seconds.  This time it could be even quicker.   No way at all to get an update out before 18240 it would fork for sure.


If you take the average 600 MGhash until the next gravity well is done, you get ~ 18 days until we reach the block 21203 - and the swing might (and probably willl) get worse.

How about block 18720?

That gives ~3 days  of 1 slow block and 2 faster blocks, so could be min 2.5 days (if hash jumps - which I doubt) or 3.5 if it slows slightly.
mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 12:16:59 PM
 #4596

i have noted that blocknumber down.....

block options are

19763
19238
18758

the blocks are located in slow periods... @ about half the retargetspan

lets first see what happens in 3 hours.

thanks
mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 12:26:13 PM
 #4597

Cant roll out another update before people have even done this one.  It will just get confusing with the number of updates being pushed out, some exchanges may even get sick of all the updates and drop the coin.

There will be a period of time when the diff swings slow the coin for a while, but long term it will resolve the issues.  So, people taking the short term view may get burned, people taking the long term view may see rewards.  Thats my opinion, but just as long as there remains enough support to pull this through the next high diff after the next multipool jump in.

People can see when gravity is coming, so as long as there are enough people keeping a bit of hash rate pointed at the coin, all will work out eventually.  Pushing out too many updates has just as much pottential to kill a coin as the multipools.

i agree with this as well.

i have the option to hold middlecoin completely off for 1  day.

if there is no other way.

whoiis
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
February 07, 2014, 12:37:10 PM
 #4598

we don't need more hash once retarget takes place
we need it once gravity has taken effect
mcg
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
February 07, 2014, 12:37:42 PM
 #4599

if we update we will do a special kind of giveaway.

i can see what ip is at what version.

so by upgrading i can reward ppl.

just give ip, i check on version.. if right version -> payment.

lot of work. but will work.

will make a quick program for this.
whoiis
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
February 07, 2014, 12:40:59 PM
 #4600

if we update we will do a special kind of giveaway.

i can see what ip is at what version.

so by upgrading i can reward ppl.

just give ip, i check on version.. if right version -> payment.

lot of work. but will work.

better reward ppl that are hammering through those last 10 shitty blocks
Pages: « 1 ... 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 [230] 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 ... 323 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!