Topic: [ANN] [DRZ] [DROIDZ] [ANTI-INSTAMINE] - A FRESH NEW START - WALLET UPDATES!!! - page 19. (Read 48442 times)
January 21, 2016, 10:03:54 PM
Nah, we just have to follow the rule of crypto and dump our shares down to 100 sats and then buy back in at 3k...
January 21, 2016, 12:53:32 PM
It is good time for quality update, is swap completely successfully done?
Are there any destroyed coins?
Bittrex news?
Are there any destroyed coins?
Bittrex news?
Dev gone. What part you guys do not understand?
January 21, 2016, 12:47:35 PM
It is good time for quality update, is swap completely successfully done?
Are there any destroyed coins?
Bittrex news?
Are there any destroyed coins?
Bittrex news?
Dev gone. What part you guys do not understand?
January 21, 2016, 12:35:05 PM
It is good time for quality update, is swap completely successfully done?
Are there any destroyed coins?
Bittrex news?
Are there any destroyed coins?
Bittrex news?
Dev gone. What part you guys do not understand?
January 21, 2016, 05:41:31 AM
It is good time for quality update, is swap completely successfully done?
Are there any destroyed coins?
Bittrex news?
Are there any destroyed coins?
Bittrex news?
January 21, 2016, 04:36:25 AM
Does anyone know when will trex resolve wallet problems?
January 20, 2016, 09:16:10 PM
i did a very simple test 
changed offending line value
https://github.com/K1G3C/Droidz-V3/blob/55f2cb40932f14349492709907dc593404799589/src/main.h#L98
to 1000,
recompiled
sent 1000 to an address,
went to console and "masternode outputs" and there she was … happy as larry
so seemingly master nodes are currently operational for amounts of 100k . lol
.. i honestly don't know if that simple change is all that's required, else it would be a simple fix then recompile for all systems.
possibly also adding a new timestamp for operations of masternode to allow more users to be ready for set time??
changed offending line value
https://github.com/K1G3C/Droidz-V3/blob/55f2cb40932f14349492709907dc593404799589/src/main.h#L98
to 1000,
recompiled
sent 1000 to an address,
went to console and "masternode outputs" and there she was … happy as larry
so seemingly master nodes are currently operational for amounts of 100k . lol
.. i honestly don't know if that simple change is all that's required, else it would be a simple fix then recompile for all systems.
possibly also adding a new timestamp for operations of masternode to allow more users to be ready for set time??
as far as i can tell - it is - and can test quite easily that way ...
BUT - it is not the official code ... and i can only assume that the amount was set so high initially so that mn testing would not happen easily at the beginning - until the whole swap has been finalized ...
so until the official 'go-ahead' with the code is given - we really shouldnt play with too much - unless its internal testing and wont affect the blockchain ...
we should hear from the core dev ( i hope ) soon ...
just another thing - we really need the poll taken off also ... i think its sorta done
...#crysx
January 20, 2016, 09:11:15 PM
i did a very simple test
changed offending line value
https://github.com/K1G3C/Droidz-V3/blob/55f2cb40932f14349492709907dc593404799589/src/main.h#L98
to 1000,
recompiled
sent 1000 to an address,
went to console and "masternode outputs" and there she was … happy as larry
so seemingly master nodes are currently operational for amounts of 100k . lol
.. i honestly don't know if that simple change is all that's required, else it would be a simple fix then recompile for all systems.
possibly also adding a new timestamp for operations of masternode to allow more users to be ready for set time??
edit ..
just realised it's probably a hard fork/mandatory update thing as well :p so not as simple as changing value .
changed offending line value
https://github.com/K1G3C/Droidz-V3/blob/55f2cb40932f14349492709907dc593404799589/src/main.h#L98
to 1000,
recompiled
sent 1000 to an address,
went to console and "masternode outputs" and there she was … happy as larry
so seemingly master nodes are currently operational for amounts of 100k . lol
.. i honestly don't know if that simple change is all that's required, else it would be a simple fix then recompile for all systems.
possibly also adding a new timestamp for operations of masternode to allow more users to be ready for set time??
edit ..
just realised it's probably a hard fork/mandatory update thing as well :p so not as simple as changing value .
January 20, 2016, 01:23:18 PM
So am I
January 20, 2016, 01:21:15 PM
Slowly refill my bag of DRZ.
Hope Bittrex resolve his issue soon.
Waiting for some fresh news.
Hope Bittrex resolve his issue soon.
Waiting for some fresh news.
January 20, 2016, 06:16:24 AM
I hope good news will flush all this negativity and give us steady rise.
We need Bittrex . Also we need more exchanges just for better distribution.
We need Bittrex . Also we need more exchanges just for better distribution.
January 20, 2016, 03:52:23 AM
I really want to trex to resolve everything sooner so we can trade drz
they will - and so will we ...
#crysx
January 20, 2016, 02:12:07 AM
I really want to trex to resolve everything sooner so we can trade drz
January 19, 2016, 07:49:25 PM
It's been four days, why DRZ remain disabled in bittrex? explanation please.
issues possibly? ...
bittrex only ever pull a market when in maintenance - repair - dissolution - or changes ...
time will tell ...
#crysx
bittrex was the one exchange not participating in swap. having their wallet disabled does perhaps mean swap time may need to be extended?
OP should be edited to reflect current state of swap as well
January 19, 2016, 07:29:38 PM
It's been four days, why DRZ remain disabled in bittrex? explanation please.
issues possibly? ...
bittrex only ever pull a market when in maintenance - repair - dissolution - or changes ...
time will tell ...
#crysx
January 19, 2016, 05:07:40 PM
It's been four days, why DRZ remain disabled in bittrex? explanation please.
RIP
January 19, 2016, 04:57:48 PM
It's been four days, why DRZ remain disabled in bittrex? explanation please.
RIP
January 19, 2016, 11:29:14 AM
It's been four days, why DRZ remain disabled in bittrex? explanation please.
January 19, 2016, 08:33:40 AM
John did you get masternode running?
ill try and start testing this tomorrow ...
#crysx
How? Do you have 100K DRZ to test with?
you can change the code to a MUCH smaller amount and recompile without affecting the main blockchain drays ...
simply test off testnet - which is completely different blockchain to the main one ... and 'test' coins instead of the real ones ...
actually - come to think of it ... i dont know what the testnet ports are ... ill find out later ...
but i havent yet recompiled as i have had no time yet to do anything ... im in the middle of a house move - and preparing for another one in 6weeks ... so im a little all over the place at the moment ... so i 'may' test this theory tomorrow ... or next week
...btw - 10kdrz is still a huge amount ... i was looking more at 1kdrz as a test
...off to bed now mate ... goodnight all ...
#crysx
January 19, 2016, 08:26:30 AM
John did you get masternode running?
ill try and start testing this tomorrow ...
#crysx
How? Do you have 100K DRZ to test with?
I tried to modify that part of code and put 10K instead (sure I didn't expect it will work by just adjusting my wallet, by tried that just for fun). The master node did start, but as one could expect, it was dropped by network very soon. I suppose that's because other nodes still expect 100K at MN. Or maybe there are other parts in code preventing it from working too.
Jump to: