Topic: 💦[RAIN]💦X11💦ONLY DL FROM GITHUB!💦20,000,000 COINS BURNED!💦condensate.co💦 - page 3. (Read 150309 times)

Mine is also.

out of sync again, new version maybe?

Im not in the Team, just a normal user....join the Discord Server, there will be a code change in the next months.....
https://discord.gg/gJKG7yn

what about reviving this coin with a good update that add something new? no buyers on exchange the coin is not getting any interest

Dont forget to update your wallet guys, still around 10 days left....

copied from discord-channel:

dmnq09.06.2020
Hi @everyone @here,

With less than 2.400 to go, we can safely say v2 of the Rain wallet will not be ready in time.
We are working out the last bugs and are (test)building several wallets to check for compatibility.

So, because block 1743000 is around the corner, @psycho-pat  was kind enough to build an 'in between' version to bump the fork block.
Release v1.1.1.5 can be downloaded from https://github.com/raipat/rain/releases/tag/v1.1.1.5

This will bump to block 1800000, which is around July 20th.

yeah i think it's safe, not getting anything suspicious, still i run all this shit in a VM, better safe than sorry

I believe it was just a virus checker error.

I have version v1.0.0.1 and there are no problems besides a lot of RAM consumption.
Rewards are coming, synchronization is on.

Getting a Botnet Blacklist virus message repeatedly coming for different wallets.
Getting this after installing new RAIN wallet.  Not sure if its related.

which also dangerous could be infected, there wasn't a new dev around that was following this coin?

No countdown, no real mention, just threw it out on people.

oh there is a new version? i'm still at 1.1.1.4...

Here is the latest from the RAIN discord:

as the tip/stake bot operator, I can tell you that syncing the rain wallet was not a particularly fast matter, even with the bootstrap, even on a super fast linux server. Read: days.
That said, I can give you a couple of suggestions.
- can you take a look at your connections? How many peers do you see? If you see a small number of peers, try getting your addnode list from the bot, such as here https://discord.com/channels/428296617544908800/428300887350575114/725812598645194832
- if the blockchain has stalled completely, and you have only a small number of peers, you might have ended up on a fork. Double check your wallet version (is it 1.1.1.5? https://github.com/raipat/rain/releases/tag/v1.1.1.5). Compare blockhashes for the latest block that you see with http://explorer.condensate.io/, if they differ you're on a fork.
- if you're on a fork, you might have to resync, but before that, you should clear out your old peers, and that would be best by moving your peers.dat somewhere else, and putting the addnode like I described in your .conf - rerun the wallet, it might continue syncing where it stalled
Hope that helps you and anyone else having wallet problems


(I've been too busy to try this)

no 20k blocks behind

Are you synced and staking?

how to see this? my number of connection is limited now

It only synced to the same point as last time then stopped.

See this thread:
https://bitcointalk.org/index.php?topic=5257834.0;topicseen

Can a corrupt team cook a blockchain?

I have some suspicion a coin I'm staking had a team take over it that "cooked it's books" somehow.   The wallet keeps stalling and will not sync, and there are others on the thread/channel that say they are able to sync and stake. This has happened a number of times since a person took over the development.  The blockchain their new coin creates never works for more than a few weeks but supposedly for a couple people it does. Many chime in on the thread that they are not able to sync.

I know behind the scenes at the code level (or maybe node level) there is a lot of control a developer can have.   Is it possible for a corrupt team to make it that only certain people are getting stakes?

replies:

Definitely a red flag and in these circumstances the wise thing is to stop staking and get rid of your inventory as soon as possible, just accept the loss and find a better coin to stake or invest in believe me there are dozens of quality coins out there, do not just go after roi consider the genuinity, reputation and quality first always.

and

It's entirely possible to allow certain IP to connect to the nodes and blacklist the rest. At this point, the only thing you can do is observe for a little longer and see how would the dev team address the issue. If they are really into fixing it, you would easily know on how they would respond to queries regarding the issue. Also, observe some of those people who reported that they are able to connect just fine without any hassles. There could be some form of collaboration between some of the stakeholders and the devs, so watch out for those too. If your suspicions are already confirmed, I suggest you dump the coins and look for other ones that has potential to grow.

This seems to happen a lot with this coin, but I'm still supporting it.  I tried the bootstrap but like with so many coins bootstrap, it doesn't work.

If you have some kind of special instructions when you create a bootstrap, SPELL THEM OUT.

Just repeat the instructions anyway.  I book the file as is in my appdata directory and it didn't work.

I'm alright. Last December, I turned off my wallet and decided to restart it. From scratch for about a week it was synchronized.
The wallet consumes 700 MB of RAM and freezes periodically and shuts down itself, but now everything is fine.
And even the reward has come)

wallet is still stuck with the last version, no more synching....