Topic: [ANN] [DRZ] [DROIDZ] [ANTI-INSTAMINE] - A FRESH NEW START - WALLET UPDATES!!! - page 5. (Read 48431 times)

why is there still people with DRZ stucked on trex? That chain is still working now? how can they  move their drz?

ill need to speak to greedyjohn tomorrow - im knackered now - so will sleep soon ...

if we can put a good sum of coin in the seednodes - they will stake heavily and keep the blockchain running smooth ...

i exchanged all mine - so i have no drz24 coin left - only drz3 ...

#crysx

Folks, the DRZ-OLD blockchain is not moving, please stake your DRZ-OLD coins if you have them in local wallet, otherwise transactions (particularly from Bittrex) will not be able to go out!! The last block was 8 hours ago.

Don`t throw your coins mate i sent my to drays.

exactly my thoughts ... are you 'throwing' your coins away? ... or are you looking at taking up one of the offers? ...

#crysx

You did not get an instant reply from me, because I was busy at work.

So.. you gave up with Drz? I can keep your DRZ, then return DRZ-NEW to you swapped after SoopY is done with the procedure. I really don't want people to leave the boat.

If anyone want drz, pm me your address. I've been pmed greedyjohn but no response.

I don't want to download the wallet and the whole blockchain.

For one person only.

Now i installed it on my virtual machine and got it to work, now everything fine thanks.

It was wallet v2.4 someone told my i need to install that one and transfer from trex.

tanx drays ...

i tested the seednodes after you suggested that there may be something wrong - and restarted the daemons anyway - just in case ...

though i didnt see any issues from the beginning - it is better to be notified in case there is and issue ... so i appreciate that ...

one thing i HAVE found that is an issue though - is the new v3 daemons ( on the same seednodes addresses ) refuse connections - even though they are on completely different ports ... they WILL communicate with one another though - which leads me to believe i may have messed the ports up and blocked all others except the three ip addresses ...

ill be checking this tomorrow as i have a huge amount to finish before i sleep tonight ...

what ports do you have set for v3? ... rpcport and p2pport? ...

edit - i think i may have found the problem ... wrong port ... and believe it or not - it was a keypad typo ... i really should not be working when im this tired ...

testing this now ... it looks like its working already ...

if so - ill re-sync the block chain new again for drz3 sync ...

edit again - yup it was fat finger syndrome ...

ports are now corrected and the three drz seeds are now syncing and will be serving the network once again ... the same addresses listed above and below are used for both versions of drz ( v2.4 and v3 ) - which now should have NO issues with sync if you add at least one of the three node addresses ( or all three ) ...


and yes - they are all under the granite umbrella and ecosystem ... crypto helping crypto ...

id also like to add to the offers that drays and greedyjohn have put forward ...

i have a limited number of systems that not only will hold the coins - but will also stay alive on the network as nodes if you wish to store your coins in those nodes ...

yes - these systems ( vps ) are on 24 / 7 under the granite ecosystem ...
yes - they will stake the coins you deposit ...
yes - you can have the whole lot when the swap is done - including any coins that have been staked ...

currently - there are only 7 systems available to do this on the granite ecosystem ... if you include drays and greedyjohns offer of storing the coins - then you have a few options here at you disposal ...

there is NO guarantee of protection from loss from hacking or otherwise - but under granite - they are on the granite network and are the same vps / secured systems that the seednodes are located on and are LOCKED OUT from access to anyone else ... no expectation of trust is requested here - but this may be an option for you if you believe that drays greedyjohn and myself are reliable trustworthy community members and wish to trust your coins with any one or all of us ...

just to clarify - we are NOT working together on this - i though i would just chime in and put the granite facilities that are available to use at this time - for the use of the some of the community members ...

pm me if you wish to discuss any options for my offer - or drays for his offer - or greedyjohn for his offer ...

#crysx

Ok, as I promised, today I re-tested the OLD-DRZ connection from new two different PC: one is behind NAT (Windows), another one in open Internet (Ubuntu).

Glad to tell they both found connections instantly as soon as I added these three nodes into the droidz.conf file:

Now they are in process of syncing. So I suppose whatever the problem was, it seems to be resolved now. The wallets have found few other connections too, so you may be safer with this node list:

First three are the same crysx nodes in IP resolved form, others are different machines, including two my public nodes, which I will leave running for some time, so network could be stronger.
************************

Note/offer: if anyone still has problems syncing, or doesn't have time to setup the wallet right now (syncing from scratch could easily take several hours), you could PM me, so I send you an address to keep your DRZ-OLD until you have time to setup the wallet (as Bittrex deadline is very close). Sure you don't have to trust anybody after everything happening with this coin , but its up to you, I just offer a solution and my help. Alternatively you could probably contact GREEDYJOHN, maybe we could also want to do the same for you.

what issues are you having with it? ...

v2.4 or v3 wallet? ...

#crysx

Mate i`m having troubles with the wallet and i don`t have time to deal with it at the moment please post me you drz address so i can sent you 5k drz.

Thanks 

The PC with that wallet is at my workplace, I don't have access to NAT router there. Can get it if I REALLY want it, but I prefer not to go overboard

Unfortunately I cannot test anything now, as its nighttime here and I am on tablet at the moment, not on PC...
Timezones can be a real hindrance sometimes...

Will test everything tomorrow, both from another PC behind another NAT (controlled by me), and from a VPS with open IP.

these are the right dns - and ips for the nodes - so you are not wrong there mate ...

ive just checked the log - and debug is telling the same story ... checked the old drz block explorer and that is behind by a little over 1.5 hours - but the seednodes are still active in the v2.4 node list - https://chainz.cryptoid.info/drzold/#!network ...

so looking into what is happening here - but it seems that the majority of v2.4 wallet holders are offline - which has slowed the block chain down quite dramatically ... but even that shouldnt stop the nodes from updating and syncing ...

below are the current getinfo details from the daemons ...

drz-seed1.granitecoin.com


drz-seed2.granitecoin.com


drz-seed3.granitecoin.com


so the blockchains are moving - are updated - and are active ... but showing as not contactable for a huge amount of time from your debug.log? ... very weird indeed ...

ill restart the daemons and see if that helps - but i need to check the ports to see if they are clashing with anything else ... as they were supposed to have been removed a while back when the swap was finished ... but - as we all know what happened has disrupted the plan and caused this 'damage control' session to take place ...

give it a few minutes and restart your wallet again - but remove all the files in your v2.4 folder - except for the .conf and the wallet.dat ... then see how this goes for the sync ...

ill watch the log files on all three seednodes to see what happens ... it 'should' request blocks from these nodes unless your wallet still sees them as not contactable ...

do you have access to port forwarding ( fro the rpcport 5125 and psp 5124) through the router to bypass nat? ...

tanx drays ...

#crysx

Meanwhile my DRZ 2.4 wallet is unable to find nodes too

I added this to droidz.conf:

But this is what I get now:

The 51.254.216.25, 51.254.216.250 and 51.254.216.251 are the drz-seed1, drz-seed2 and drz-seed3 appropriately..
Not sure whats wrong. Hopefully that is just my local wallet, but... crysx, could you please check the nodes just in case?

I'll try later from another machine, as this one is behind NAT and wallets running on it often have connection issues.

same - though the hashes supplied were from thefarm and not from any hash rentals ... so spending btc on renting hash will be a waste if it remains this way ...

which proves that what you are saying is right ... the wallet code needs tweaking / fixing - and soopy is working on that as we chat here ...

save your btc mate - and use it to buy more drz instead ... ...

this will eventually happen ...

#crysx

I think the problem is not in the hash or rigs, but in the wallet itself. The hash I rented from Nicehash (proxied through my own pool, converted to "getwork" protocol and redirected to SoopY's wallet was able to find several block candidates, but all of them were rejected by the wallet buy unknown reason. The sahers were accepted well, but found blocks were rejected.

I suppose SooPy is working now to fix something related to this...