Symbol tweet update

Symbol blockchain news update – 04/08/21

Hi everyone and welcome to Wednesday’s Symbol Blog news update! It is a little rushed again today so I have probably missed things and there may be typos throughout (sorry)! My son’s nursery is closed due to (another) COVID outbreak so I am splitting my time between work, childcare and blog writing. I need a holiday! 😆

Sharing knowledge

Love this tweet from @xembook!

I believe that one of the conditions for the growth of open source projects is the “voluntary sharing of development know-how by the community”. I have been focusing on this point since 2017, and I feel that it has definitely “ignited” in the last few weeks.

There is no stopping NEM Symbol now.

@xembook (automatic translation!)

I feel the same way. The more we share, the more we collectively learn. I have really enjoyed translating @xembook‘s Python tutorials and feel like I have learnt a lot from them. I will endeavour to translate and explain technical articles to the English speaking world – please talk to us and let us know if you know what we are currently missing!

I was actually playing around today with aggregate transactions and building on this article:

I managed to set up two XYM to mosaic transfers between Alice, Bob and Carol so that Alice had enough of the mosaic to trade with Dave for a subscription to a service which was then written to Alice’s account as metadata. It was actually really easy to do and I am beginning to see the power of aggregate transactions. Maybe I will write this up after I make a post about Symbol metadata – actually I think xembook might have one so that will be next in line for translation! 😊

Symbol development in Python guides

Oh and if you are interested in taking your first steps in developing on Symbol using Python you can find all of our guides here.

Thanks again to all of the original authors, I hope that my translations are OK. To anyone following the guides, we welcome your feedback. If you have your own guides that you would like to share then let us know!

Web integration of Symbol payments

I saw this tweet from @bestgoldangel which links to quite a comprehensive guide to implementing a web-based Symbol payment system in TypeScript. As usual it is in Japanese but Google Translate does a reasonable job here and you should be able to follow it.

I would try to translate but there is a lot of Japanese text and I’m not sure I fancy getting my head around TypeScript too! The code is available on GitHub so go check it out!

Taking suggestions

What do you want to hear about from @0x6861746366574 (Hatchet)? She has promised me a guest post on Symbol Blog (I will hold you to that! 😁). Not sure if this tweet relates to this, or if it rhetorical but it seems to me like an invitation to the community for input on ideas for an article so let her know! 😊

Price talk & exchanges

Since starting writing the blog I haven’t been as obsessed as I once was with checking the Symbol price (I am probably too busy!). This tweet from @TrendStream seems to show some early encouraging signs though. Personally I am pretty confident that the days of cheap XYM will not last too long.

It is also good to see the team actively helping exchanges integrate Symbol. I wonder which exchanges are coming next.

As Hatchet mentions, having an active and vibrant community really matters here so get involved!

It seems that there are active discussions about this on Discord so hopefully we will see more exchange listings soon.

And finally..

Just a reminder, if you have more than 10,000 XYM then you should be harvesting! You can earn XYM for doing nothing!

Thanks!

Once again, thank you for reading and we will be back tomorrow (my birthday! 🥳) with another post!

Avatar photo
NineLives
admin@symbolblog.com

I'm a Symbol and NEM enthusiast and run this blog to try to grow awareness of the platform in the English-speaking world. If you have any Symbol news you would like me to report on or you have an article that you would like to publish then please let me know!

No Comments

Sorry, the comment form is closed at this time.