June 10, 2020

By Cayle Sharrock

Stress testing and emoji changes

Emoji set changes

Weโ€™ve merged changes into the core emoji set! The reasons for this are:

  • Some emoji werenโ€™t supported on older Android devices.
  • A few emoji have issues when being copied / pasted into common chat apps.

The set weโ€™ve now proposed has been thoroughly tested and has minimal issues in most common chat apps.

So what does this mean?

It means your emoji ID is going to change. Sorry. ๐Ÿ˜ฟ

But nothing else really changes, and nothing really breaks.

Hereโ€™s why:

Your emoji id is an encoding of your node or wallet id on the network. The underlying node id isnโ€™t going to change (unless you re-install the app from scratch), just its representation.Think of it like this - If you use Google to translate what you ate for breakfast from English to Portuguese, the words on the screen change, but the underlying meaning hasnโ€™t changed. Thatโ€™s basically what this emoji set update represents.

So this means that you keep your testnet funds, and everything works as before. You contacts will automatically update to reflect their new emoji ids too.

In fact, the only thing that wonโ€™t work is if you paste an emoji id into your wallet that was copied from an older version of the app, and vice versa. And even if that happens, the new version of Aurora will detect the older format and warn you about it.

Whatโ€™s actually changing?

Ok, so here are the emojis that have been removed (131 in total). If they arenโ€™t displaying on your device properly as you read this, youโ€™ll understand why they were removed:

๐Ÿ˜€ ๐Ÿคฃ ๐Ÿ˜Š ๐Ÿ˜˜ ๐Ÿค— ๐Ÿคฉ ๐Ÿค” ๐Ÿ™„ ๐Ÿ˜ฎ ๐Ÿค ๐Ÿ˜ด ๐Ÿ˜› ๐Ÿคค ๐Ÿ™ƒ ๐Ÿค‘ ๐Ÿ˜ค ๐Ÿ˜จ ๐Ÿคฏ ๐Ÿ˜ฌ ๐Ÿคช ๐Ÿ˜ต ๐Ÿคข ๐Ÿคฎ ๐Ÿค  ๐Ÿคก ๐Ÿคซ 
๐Ÿคญ ๐Ÿค“ ๐Ÿค– ๐Ÿ˜บ ๐Ÿ‘ถ ๐Ÿ‘ฉ ๐Ÿ‘จ ๐Ÿ‘ฎ ๐Ÿคด ๐Ÿ‘ธ ๐Ÿงœ ๐Ÿ™… ๐Ÿ™‹ ๐Ÿคฆ ๐Ÿคท ๐Ÿ’‡ ๐Ÿƒ ๐Ÿ’ƒ ๐Ÿง— ๐Ÿ›€ ๐Ÿ›Œ ๐Ÿ‘ค ๐Ÿ„ ๐Ÿšด ๐Ÿคน ๐Ÿ’ 
๐Ÿ‘ช ๐Ÿ’ช ๐Ÿ‘ˆ ๐Ÿ‘ โœ‹ ๐Ÿ‘Š ๐Ÿ‘ ๐Ÿ™ ๐Ÿค ๐Ÿ’… ๐Ÿ‘‚ ๐Ÿง  ๐Ÿ‘„ ๐Ÿ’– ๐Ÿ’™ ๐Ÿ’ฅ ๐Ÿ’ซ ๐Ÿงฃ ๐Ÿงค ๐Ÿงฆ ๐Ÿ‘œ ๐Ÿงข ๐Ÿ’ ๐Ÿฆ ๐Ÿฆ„ ๐Ÿซ 
๐Ÿฆ’ ๐Ÿ‡ ๐Ÿ” ๐Ÿฆ† ๐Ÿฆ€ ๐Ÿฆ‹ ๐ŸŒฒ ๐Ÿฅ‘ ๐Ÿฅ• ๐Ÿฅœ ๐Ÿง€ ๐Ÿ– ๐Ÿฟ โ›บ ๐Ÿš” โ›ฝ โ›ต ๐Ÿ›ซ ๐Ÿ›ธ โŒ› โฐ ๐Ÿ•™ ๐ŸŒ› โ›… โœจ ๐Ÿ… 
โšฝ ๐ŸฅŠ ๐ŸŽฏ โ›ณ ๐Ÿ”ˆ ๐ŸŽถ ๐Ÿ“ป ๐Ÿฅ ๐Ÿ” ๐Ÿ“– ๐Ÿ“… ๐Ÿ”’ ๐Ÿน ๐Ÿง โ›” โœ… โŒ โ“ โ• ๐Ÿ†— ๐Ÿ†˜ โฌ› ๐Ÿ”ถ ๐Ÿ”ต ๐Ÿšฉ ๐ŸŽŒ ๐Ÿด

These are newly introduced into the set (131 in total):

๐ŸŒŠ ๐ŸŒ™ ๐ŸŒ ๐ŸŒŸ ๐ŸŒ  ๐ŸŒฐ ๐ŸŒด ๐ŸŒท ๐ŸŒน ๐ŸŒป ๐Ÿ€ ๐Ÿ ๐Ÿ… ๐Ÿ† ๐Ÿˆ ๐ŸŠ ๐Ÿ‹ ๐Ÿ ๐Ÿ ๐Ÿ‘ ๐Ÿ— ๐Ÿš ๐Ÿ  ๐Ÿฃ ๐Ÿฉ ๐Ÿญ 
๐Ÿฏ ๐Ÿณ ๐Ÿต ๐Ÿถ ๐Ÿธ ๐Ÿน ๐Ÿผ ๐ŸŽ‚ ๐ŸŽƒ ๐ŸŽ„ ๐ŸŽ“ ๐ŸŽ  ๐ŸŽฅ ๐ŸŽฉ ๐ŸŽช ๐ŸŽฌ ๐ŸŽญ ๐ŸŽฐ ๐ŸŽฑ ๐ŸŽณ ๐ŸŽต ๐ŸŽท ๐ŸŽผ ๐ŸŽฝ ๐ŸŽฟ ๐Ÿ‰ 
๐Ÿฅ ๐Ÿฆ ๐Ÿญ ๐Ÿฐ ๐Ÿ€ ๐Ÿ‰ ๐ŸŠ ๐ŸŽ ๐Ÿ ๐Ÿ“ ๐Ÿ– ๐Ÿ— ๐Ÿ™ ๐Ÿ› ๐Ÿœ ๐Ÿ ๐Ÿž ๐Ÿข ๐Ÿฃ ๐Ÿจ ๐Ÿฉ ๐Ÿช ๐Ÿฌ ๐Ÿฏ ๐Ÿฐ ๐Ÿฒ 
๐Ÿต ๐Ÿบ ๐Ÿป ๐Ÿผ ๐Ÿฝ ๐Ÿพ ๐Ÿ‘… ๐Ÿ‘’ ๐Ÿ‘“ ๐Ÿ‘˜ ๐Ÿ‘š ๐Ÿ‘› ๐Ÿ‘ž ๐Ÿ‘Ÿ ๐Ÿ‘  ๐Ÿ‘ก ๐Ÿ‘ข ๐Ÿ‘ฃ ๐Ÿ‘น ๐Ÿ‘พ ๐Ÿ‘ฟ ๐Ÿ’€ ๐Ÿ’„ ๐Ÿ’ˆ ๐Ÿ’‹ ๐Ÿ’ 
๐Ÿ’• ๐Ÿ’˜ ๐Ÿ’ญ ๐Ÿ’ฐ ๐Ÿ’ณ ๐Ÿ’ธ ๐Ÿ’ผ ๐Ÿ“ˆ ๐Ÿ“‰ ๐Ÿ“ฃ ๐Ÿ”Œ ๐Ÿ”Ž ๐Ÿ”ฉ ๐Ÿ”ช ๐Ÿ”ซ ๐Ÿ”ฌ ๐Ÿ”ฎ ๐Ÿ”ฑ ๐Ÿ—ฝ ๐Ÿ˜‡ ๐Ÿ˜น ๐Ÿ˜ป ๐Ÿ˜ฟ ๐Ÿš“ ๐Ÿš— ๐Ÿšจ ๐Ÿ›

And these are unchanged (125 in total):

๐Ÿ˜‚ ๐Ÿ˜‰ ๐Ÿ˜Ž ๐Ÿ˜ ๐Ÿ˜ฑ ๐Ÿ˜ท ๐Ÿ˜ˆ ๐Ÿ‘ป ๐Ÿ‘ฝ ๐Ÿ’ฉ ๐Ÿ‘€ ๐Ÿ’” ๐Ÿ’Œ ๐Ÿ’ค ๐Ÿ’ฃ ๐Ÿ’ฆ ๐Ÿ’จ ๐Ÿ‘” ๐Ÿ‘• ๐Ÿ‘– ๐Ÿ‘— ๐Ÿ‘™ ๐ŸŽ’ ๐Ÿ‘‘ ๐Ÿ’ ๐Ÿ’Ž 
๐Ÿถ ๐Ÿด ๐Ÿฎ ๐Ÿท ๐Ÿ‘ ๐Ÿ˜ ๐Ÿญ ๐Ÿธ ๐Ÿ ๐Ÿณ ๐Ÿš ๐ŸŒ ๐ŸŒธ ๐ŸŒต ๐Ÿ‡ ๐Ÿ‰ ๐ŸŒ ๐ŸŽ ๐Ÿ’ ๐Ÿ“ ๐ŸŒฝ ๐Ÿ„ ๐Ÿž ๐Ÿ” ๐ŸŸ ๐Ÿ• 
๐Ÿฆ ๐Ÿช ๐Ÿฐ ๐Ÿซ ๐Ÿฌ ๐Ÿท ๐Ÿบ ๐Ÿด ๐ŸŒ ๐ŸŒ‹ ๐Ÿ  ๐ŸŽก ๐ŸŽข ๐ŸŽจ ๐Ÿš‚ ๐ŸšŒ ๐Ÿš‘ ๐Ÿš’ ๐Ÿš• ๐Ÿšœ ๐Ÿšฒ ๐Ÿšฆ ๐Ÿšง ๐Ÿšข ๐Ÿ’บ ๐Ÿš 
๐Ÿš€ ๐Ÿšช ๐Ÿšฝ ๐Ÿšฟ ๐ŸŒž ๐ŸŒ€ ๐ŸŒˆ ๐ŸŒ‚ ๐Ÿ”ฅ ๐ŸŽˆ ๐ŸŽ‰ ๐ŸŽ€ ๐ŸŽ ๐Ÿ† ๐Ÿ€ ๐Ÿˆ ๐ŸŽพ ๐ŸŽฃ ๐ŸŽฎ ๐ŸŽฒ ๐Ÿ”” ๐ŸŽค ๐ŸŽง ๐ŸŽธ ๐ŸŽน ๐ŸŽบ 
๐ŸŽป ๐Ÿ“ฑ ๐Ÿ”‹ ๐Ÿ’ป ๐Ÿ“ท ๐Ÿ”ญ ๐Ÿ“ก ๐Ÿ’ก ๐Ÿ”ฆ ๐Ÿ“š ๐Ÿ“ ๐Ÿ“Œ ๐Ÿ“Ž ๐Ÿ”‘ ๐Ÿ”จ ๐Ÿ”ง ๐Ÿ’‰ ๐Ÿ’Š ๐Ÿšซ ๐Ÿ’ฏ ๐Ÿ

When will this happen?

These changes will be introduced in the next minor release of the mobile (0.2.0) and base node (0.4.0) apps and weโ€™ll let you know when those drop so that everyone can upgrade expeditiously; most likely late next week, but weโ€™ll keep you posted.

Stress testing - part II

The developer community ran a second testnet stress test this week. (Say that 10 ten times quickly).

The test dumped 48,000 transactions onto the Tari network in the space of a few minutes. Things went much better than the first test (that test amounted to a self-inflicted DDoS attack):

  • A large majority of transactions got signed and broadcast.
  • A majority of transactions were broadcast on the network, with mempools filling up nicely.
  • Nodes did not fail under intense memory or CPU consumption, and blocks were successfully propagated through the network.

Even though this was a vast improvement over the first test, the results are still not where we want them to be. If youโ€™re interested in the technical minutae, you can jump into #tari-dev and follow the conversation there.

The good news is that the remaining problems are somewhat self-evident. Several core contributors have already started to address those issues and we are hoping to see further massive improvements in the next stress test.

Reminder - Telegram discussion this Friday

The Tari community will be discussing the Proof of Work for mainnet this friday. Join us and make your voice heard.

Friday, June 12th @ 16:00 UTC (9:00 PDT, 12:00 EDT, 17:00 CET, 18:00 SAST) on Telegram or #Tari on Freenode* to discuss the proof-of-work algorithm for Tari.

*There is a bridge routing messages from either platform to each other