Topic: [MIL]* MillenniumCoin DAAE * TOR * Anon * Escrow "NEW GROUND FOR CRYPTO" - page 11. (Read 26308 times)

Thanks for the update YarkoL.

A whitepaper could help a lot in explaining the technology behind MIL. The roadmap will let everyone know where MIL is headed. That will make it easy for the press to check out and test MIL.

If there are no major problems with MIL especially the delegate feature, it maybe time to start contacting sites that review digital coins. Writing blog articles about MIL here and there might also help.

The recent test brought up a minor issue in delegate selection,
which is hardly consequential, unless you do a lots of delegate transactions at once.
This will be fixed of course.

I'm currently refactoring the some of the code and working towards the next release.
I can't give any ETA for that except "soon-ish"..  my free time is a little limited
at the moment.

But, before that I hope to put up the whitepaper. It will also give an outline
of the future development and you will see a roadmap at that time.

My thoughts on promoting: in short, everyone is free to promote MIL. And I see
in these forums that lots of energy goes into promoting coins instead of getting
real users for them, in the real world. I think that's totally backwards, and I think
MIL could make a difference here.

Any news on the recent test? Has the network and staking stabilized?

What's next for MIL coin in terms of marketing, promotion, and technical development?

Everyone is free to put up a delegate.

So... I can't delegate yet? I set it up though... Shouldn't I yet?

Devvie
twitter.com/devnullius

Poloniex Deposits and Withdrawals have resumed. Be sure to keep your MIL in the DAAE wallet if you do not plan to trade. You will be rewarded by staking and additionally rewarded by setting up your wallet to be used for delegate transfers. We plan to extensively test the delegate functions next week so rewards will be much higher than normal. For example, 1000 MIL transfer by delegate will cost the sender 3 MIL. This cost is to pay the delegate who is used for the transaction. Below are the current delegates who will be paid during the testing. Don't miss out on easy MIL!!!

"address" : "fidikevyotzv22pz.onion",
"balance" : 4431.00764269

"address" : "jk2icq3nhoillqyl.onion",
"balance" : 6068.57645038

"address" : "mm2cwrpnbcopkzto.onion",
"balance" : 5.99269163

"address" : "rlnl6dnz6uaovpaf.onion",
"balance" : 1879.98075085

"address" : "uxyazroipdst5hca.onion",
"balance" : 8269.94333060

"address" : "xuf4aiy6fsct6abu.onion",
"balance" : 5000.00000000

"address" : "z23q7ggwbimlfj6c.onion",
"balance" : 5002.23964124

"address" : "4xpof3ji567tjzlg.onion",
"balance" : 9756.88619433

When trading on another exchange?

I also can now connect, sync and stake with the MIL network.

I deleted all files except the Millennium.conf and wallet.dat files and run the new MIL wallet and let it connect and sync. My original wallet files were from the old wallet. I don't know if that was the cause of all my troubles because it was working fine before.

I also have a problem with the color scheme of the new wallet. It is too black. I can't see if an option is already checked or not.

The advertised balance is a percentage of your
spendable balance. It does not affect staking.

If someone's wallet chooses your wallet as a delegate
when sending by delegate you earn a delegate fee, so yes,
in this way you earn MIL automatically

On my machine and on those where I have tested the
wallet, it's been grey on black. But you're now the second person
who has told me that he's finding it difficult to read, which means
that the color scheme will be altered in next release

Ah, that explains why setup didn't work for me and I had to extract the msi with 7zip Never thought of looking for a new folder on my desktop ;p

More importantly, running on W2K12R2... Why is the wallet so "dark" - for example, I cannot set up options because all is black: and I cannot read black on black Little bug?

And could explain how the delegation works? If I set it to 75%, will I only get PoS on 25%? And is this an automated way for me to earn some more Millennium...? Should the wallet be fully unlocked for delegation to work?


Devvie
twitter.com/devnullius

Yes. I have mine as well. Good work YarkoL.

Can confirm.  I see my coins in my wallet now.

Transfers from/to Poloniex ought to be
working again.

great work,Yarkol!

Thank you Ianshop, that's valuable info.


It tries to connect to itself, then hang up.
I remember this happening with the earlier version
sometime and I'd better check if something is
still allowing this kind of bizarre behavior to happen
with the recent wallet.


put addnode=eo4nn4b4xo5apyjl.onion
there too.

I encountered this before and I remember leaving the computer overnight and after I wake up, I found the wallet already in sync with the network. Unfortunately, that does not work anymore.

How about the others, can you connect and sync easily with the MIL network?

I noticed the new MIL wallet changes the conf file to:

addnode=fidikevyotzv22pz.onion
paytxfee=0.01


Are those two entries enough?

After successfully connecting and synching with the MIL network 4 days ago, I failed to connect the following day. I've been trying since then but still no luck. I only get the following logs and the wallet becomes unresponsive but using 25% of the CPU processing. I'm pretty sure it's not my DSL connectin because I can sync with the URO network just fine which was 7 weeks behind when I started the URO wallet.


ThreadDNSAddressSeed exited
SOCKS5 connecting fidikevyotzv22pz.onion
Flushed 15 addresses to peers.dat  41ms
SOCKS5 connected fidikevyotzv22pz.onion
refreshWallet
ipcThread started
accepted connection 127.0.0.1:60567
send version message: version 60014, blocks=346759, us=ubkrxvwi4e6tkdh6.onion:35552, them=0.0.0.0:0, peer=127.0.0.1:60567
Added time data, samples 2, offset +5 (+0 minutes)
socket inactivity timeout
disconnecting node 127.0.0.1
accepted connection 127.0.0.1:52128
socket no message in first 60 seconds, 1 0
disconnecting node 127.0.0.1
accepted connection 127.0.0.1:52984
socket no message in first 60 seconds, 1 0
disconnecting node 127.0.0.1
accepted connection 127.0.0.1:53929
socket no message in first 60 seconds, 1 0
disconnecting node 127.0.0.1
accepted connection 127.0.0.1:55386
socket no message in first 60 seconds, 1 0
disconnecting node 127.0.0.1
accepted connection 127.0.0.1:56728
socket closed
disconnecting node 127.0.0.1

Regarding the Poloniex, it's a little hard to get to the root
of the trouble,  as we are separated by ocean, and tests need to be done
and logs read, and at their end they're probably very
busy.

But rest assured the issue will see a resolution,
and despite gaps in communication I'm working towards
it all the time.

Also if anyone else is having connectivity problems, let
me know.

In fact if you have any questions at all concerning MIL,
let me know that too. 

Doesn't seems to be.

So, is it fixed?