Pages:
Author

Topic: [SNRG] 🔥 Synergy 🔥 Cloud.Synergycoin.com Cloud Bot Now Live!! 🔥 - page 44. (Read 162153 times)

full member
Activity: 224
Merit: 100
Is the blockexplorer up to date?  Even with the update, we're at a different spot right now:

    "version" : "v1.1.1.0",
    "protocolversion" : 62002,
    "walletversion" : 60000,
    "blocks" : 40031,

getblockhash 40031
34abe67e1740a5370db785c2ed70fdb04666f1237a22d1cfb65b6d19afe168b9

Thanks,
richie@bittrex

Cryptobe has not yet updated, however, I can confirm the blockhash you have above is correct.

We expect that the explorer will be updated soon. 
hero member
Activity: 843
Merit: 1004
Is the blockexplorer up to date?  Even with the update, we're at a different spot right now:

    "version" : "v1.1.1.0",
    "protocolversion" : 62002,
    "walletversion" : 60000,
    "blocks" : 40031,

getblockhash 40031
34abe67e1740a5370db785c2ed70fdb04666f1237a22d1cfb65b6d19afe168b9

Thanks,
richie@bittrex

Same for me, anything wrong with that?
hero member
Activity: 937
Merit: 1000
Is the blockexplorer up to date?  Even with the update, we're at a different spot right now:

    "version" : "v1.1.1.0",
    "protocolversion" : 62002,
    "walletversion" : 60000,
    "blocks" : 40031,

getblockhash 40031
34abe67e1740a5370db785c2ed70fdb04666f1237a22d1cfb65b6d19afe168b9

Thanks,
richie@bittrex
newbie
Activity: 31
Merit: 0
how often will these pumps occur?
newbie
Activity: 27
Merit: 0
this is AWESOME!  i knew you'd have somethign sweet to release soon!
full member
Activity: 224
Merit: 100
my walet not synced - ver 1.1.1.0
need to more node addressess

It may take a few minutes to get a connection. This wallet runs behind Tor. Are you certain that your ISP is not blocking Tor for you? It will help if you delete your onion and tor directories and peer.dat file in your application data folder between restarts.
legendary
Activity: 1820
Merit: 1092
~Full-Time Minter since 2016~
my walet not synced - ver 1.1.1.0
need to more node addressess

hmm mine synced np straight from the mega DL, weird. im just waiting on trex to finish wallet maintence to add a few more of these to my wallet Smiley great way to add extra value to holding SNRG Cheesy
sr. member
Activity: 299
Merit: 250
my walet not synced - ver 1.1.1.0
need to more node addressess
sr. member
Activity: 462
Merit: 250

This new tab is the beginning of Grandpa's Decentralized Pump Group


I am REALLY interested to see where this goes given all of the big "movement" in the markets lately.  I'm sure I'll have a few questions tomorrow when I wake up.  Thanks for fixing the wallet, I'm going to update now.

full member
Activity: 224
Merit: 100

New Release: Low Diff Syncronization Fix


This new version fixes a problem with syncronization when the PoS difficulty gets too low.


The source and Qt links in the OP have been updated to v1.1.1.0 (protocol version 62002), please update the latest version ASAP.


You will also notice an additional tab in the Qt that was not present in the past. 

This new tab is the beginning of Grandpa's Decentralized Pump Group.  The styling/formatting will be updated and the fields will become functional in the next update. I decided to leave the tab in for today's bug fix because it would be too much trouble to take out. Please be assured that it will look much better with the next release in a few days. Complete details along with a dedicated website will be coming soon.  Please stay tuned to the thread for more information.



Below are a few common questions and answers, please add questions in the thread and we will update with a response.

How much will it cost me to join the group?
For each round, 2 SNRG.  This is simply to cover transaction costs for communication.  Yes, you read that correct, 2 SNRG (.00008634 BTC at time of posting).

Why should I join?  There are other paid groups out there.
The majority of what you are seeing in those threads are posts by shill accounts and results are fabricated.  This group will have anonymous members, only identifiable by their SNRG address.  Once the coin is chosen, the fate of the pump is completely up to the market to decide what happens.  Also, we only "charge" 2 SNRG as explained above.

How do I become eligible to participate?
Simply hold SNRG in your wallet and follow the instructions to enter for each round.  Step-by-step instructions will be provided upon opening of first round.

How many SNRG do I need to hold?
Levels within the group will be determined based on the balance of the address you register and verify each round.  The more you hold, the earlier you'll receive the tip.  Additional details for levels to be released soon.

How will coins be chosen?
The team and I will evaluate and determine the coins.  We will look for coins that are not on a high from a pump and have been "baselining" for a while. These coins will be easily pumped, low cap, but have active devs and communities. In short, they will have all the features of a breakout coin that only needs a gentle push up to explode.  If you have suggestions, please let us know via PM.

How and when will I receive notification of the chosen coin?
You will receive the encrypted notification in your Qt in the new panel when the time has come for your level.  Wallets holding more SNRG will be notified first.

How is this group "decentralized"?
The mechanism to control registration and ensure you are part of the group is decentralized.  You must have a balance to receive the notification of the coin to be pumped.  The decentralized ledger is also used for encrypted communication.

Will you tell me when to buy/sell?
No. But you will want to do both before others. Your success during the pump comes from having early knowledge which will be determined by your balance.

What can I do to help make this successful?
Spread the word about SNRG and the group!  The more people that join, the more successful everyone will be.
full member
Activity: 224
Merit: 100
Let's hope we get the update tonight.  Trex is still locked.

I am typing up the ANN now. Github was updated earlier today. Trex was notified nearly 11 hours ago. They may be waiting for an official release.
newbie
Activity: 13
Merit: 0
Let's hope we get the update tonight.  Trex is still locked.
legendary
Activity: 1218
Merit: 1002
Supporting DMD, ERC & PIO
Followed instructions above. Synched right away.
Thank you!
full member
Activity: 168
Merit: 100
The repository has been updated with the bug fix, fully tested on 3 platforms.

Mac, Windows, and Linux builds will be available in about 8 hours.

This bug turned out to be a simple typo that was exceedingly hard to track down.

You can see the key change here at github:



The typo was that I wrote "nTime" instead of "nBlockTime". One can see that both are in the call signature. This typo resulted in two different work calculations, one for retarget and one for block validation. Unfortunately the work calculation for block validation was more stringent than the one for retarget, causing good blocks to be rejected and, worse, nodes to ban each other.

This bug only manifests when the difficulty decreases to the block validation target limit, which appears to be happening. So it is a problem with changing diff, but not in the way I previously assumed (I should have checked my assumption!). The problem was exacerbated by the network's breaking up because this break-up caused the overall diff to plummet.

If you build from source, you can sync easiest by deleting peers.dat, the tor directory, and the onion directory in your application folder before starting the new client.


Shit happens!  Will wait for the update!
full member
Activity: 224
Merit: 100
The repository has been updated with the bug fix, fully tested on 3 platforms.

Mac, Windows, and Linux builds will be available in about 8 hours.

This bug turned out to be a simple typo that was exceedingly hard to track down.

You can see the key change here at github:



The typo was that I wrote "nTime" instead of "nBlockTime". One can see that both are in the call signature. This typo resulted in two different work calculations, one for retarget and one for block validation. Unfortunately the work calculation for block validation was more stringent than the one for retarget, causing good blocks to be rejected and, worse, nodes to ban each other.

This bug only manifests when the difficulty decreases to the block validation target limit, which appears to be happening. So it is a problem with changing diff, but not in the way I previously assumed (I should have checked my assumption!). The problem was exacerbated by the network's breaking up because this break-up caused the overall diff to plummet.

If you build from source, you can sync easiest by deleting peers.dat, the tor directory, and the onion directory in your application folder before starting the new client.
sr. member
Activity: 462
Merit: 250

If anyone is watching the repo, it will not be worth your time to update until I announce a release here (estimated: about 14 hours). I often push changes to the repo between releases because it helps me manage the various platforms we deploy on. Unless we make a specific release announcement, please assume for now that the repository has incomplete or non-working code.

I will try to keep such circumstances to a minimum.


Thanks for the update, I'm a win user anyways so it doesn't matter.  Grin
member
Activity: 120
Merit: 10
thank you from ho lee for attention to issue.

look forward to stake again.
full member
Activity: 224
Merit: 100

If anyone is watching the repo, it will not be worth your time to update until I announce a release here (estimated: about 14 hours). I often push changes to the repo between releases because it helps me manage the various platforms we deploy on. Unless we make a specific release announcement, please assume for now that the repository has incomplete or non-working code.

I will try to keep such circumstances to a minimum.
full member
Activity: 224
Merit: 100

This bug is a little more complicated than I thought. It will be at least another day before we release a fix.
hero member
Activity: 1064
Merit: 500
MOBU

I've got a fix for this problem now. I'll try to get it out within the next 6 hours, but more realistically it will be about 12 hours because I didn't plan on this today. I discovered it very late yesterday even though it started effecting some users over 24 hours ago.

This problem surfaced because network weight is skyrocketing because more coins are being used for staking. It blew up the network when network weight hit a critical point for the current work calculation. The fix has been simply to account for the possibility of higher weight in this calculation.


Looking forward to the fix...Thanks for the update.
Pages:
Jump to: