Switch to NxtForum

Play as much as you can! Increase your total amount wagered and get closer to win the main prize. All games and cryptocurrencies accepted (except LUCKY-tokens). The bets made before the contest start date are not taken.

Follow the Contests page for live Leaderboard and countdown timer.

All VIP players can take up to 3,000 satoshis from faucet every half an hour and up to 2K Lucky-tokens.
You can become VIP by purchasing it from our store, win one in the contest or from the VIP bot in the chat every 2 hours.

Play now at Luckygames!

Can anyone do better? 
Happy weekend!
https://ardor.rocks/2019/03/17/meme-competition-ranking/

Probably not an option at all, but what about how CloudFlare uses lava lamps for cryptography? Could something similar be used?
 
https://www.wired.com/story/cloudflare-lava-lamps-protect-from-hackers/

A small suggestion,I want to know the moment when my lease get expired,so I can setup a alert,but right now I can only see expired block,like

Your account effective balance is leased out for the next xxxxxx blocks (until block xxxxxx) to account ARDOR-XXXX-XXXX-XXXX-XXXXX

Which is not very convenience for people,so can you also add a expired time? Thank you!

What if a e.g. 20 random users can provide a random word which then will randomly be put together to a passphrase/new address and prove of this will be stored on the blockchain.

no one would know who participated, which words were sent in and in which sequence.

would that work?

This is getting much more controversial. Will be harder to persuade everyone that the 20 users are chosen at random

I would go this way:
1. Let's say, starting from block 644000, take the last number (or which ever) from the next 5 blocks ID's. Last number of 644001 is A, 644002 is B,....,644005 is E.
2. By combining these five numbers, you get block height ABCDE.
3. Get that block hash.
4. combine previous block hash, ABCDE block hash and next block hash. Sha256 that set and get some public key.
5. Generate account ID from this generated public key.
Is that makes sense?

It makes sense, actually this looks like @riker 's approach. We can go with this ceremony too. My ceremony looks more simple to me, but maybe it will cause controversy.

Besides being slightly more complicated, another problem with your approach is that not all 256 bit numbers are canonical public keys. So there is some probability that we end up with a non-canonical public key and that we have to repeat the ceremony. Since I don't understand cryptography, I'm not sure what exactly is the probability, but it is significant - maybe 50%.