Polish Whitepaper – Biała księga w języku polskim

In another fantastic community effort, the Saito Whitepaper has been translated into Polish. This is a fantastic effort and we’d like to thank @szpiegotka in particular for his efforts. If you would like to get involved, head over to the wiki to connect.

I am personally pleased not only to see the Whitepaper in one of my ancestoral languages (my Grandfather was a Wongtschowski) but also in the language of Jan Łukasiewicz and Alfred Tarski. These two Polish logicians formed an big part in my early conversion from Mathematics student to Philosophy major. They both demonstrated how rigourous tools can be brought to thinking, and also where the limits of where algebras and symbolic notations can get us.

This translation joins French and Arabic in our growing list.

The post Saito Whitepaper – Polish Translation appeared first on Saito.

We’d like to Announce the Saito Community Chess League

We know Saitozens are a smart bunch – but who is the smartest of them all?
(or best at Chess, at least).

Join Now! And start playing today.

Details:

The League will run for a month. The top players from the league stage will be pitted against each other in a tournament.

Rules:

• You can register through this form, it will allow players to select either easy mode or hard more for their participation.
  Auto Mode: In auto mode players will be matched by timezones to make it as comfortable as possible to set up games.
  Manual Mode: In manual mode players will be given access to a list of players and matchmake by themselves.
• Every player starts with a default 1500 MMR.
• Players will have their games scheduled for them by the league organizer, or they can manually invite opponents and report the results depending on which mode they chose.
• Players will need a minimum of 5 played matches to qualify for the tournament playoffs.
• Official matches will be reported through the auto-filled form by the winning player.
• Failure to play enough games by the deadline will result in reduction of MMR.

Following Through with the community

We are looking for community volunteers passionate about the arcade to run tournaments in our other games to help us develop our tournament format even further and to enrich the community with activities.

The post Saito Chess League Announcement appeared first on Saito.

1. it is the first “Saito Implementation Proposal” worthy of public discussion
2. it has fascinating implications for core blockchain properties
3. it shows why community engagement matters so much for Saito

The full proposal in is a new Github repository we have created. In the interest of sharing some technical background that might help explain this proposal, let us start this blog post with some background information on how our current codebase handles staking. Essentially, our staking mechanism has the Blockchain (class) create an in-memory data-structure which contains all the UTXO slips that users have deposited for staking. Nodes keep this data-structure in sync and select which participants get paid based on the randomness contained in the golden tickets. Users deposit tokens into this data-structure by sending specially-formatted transactions into the network. They withdraw their tokens using a second type of special transaction.

In this approach, most of the work involved in developing the staking mechanism is writing the code that manages this separate data-structure and inserts and removes UTXO from it. There are many unknowns in this approach largely around performance at scale: what data structures are ideal, how many slips it reasonably includes, what are the performance implications on the speed of block processing when we need to update this staking table when we add a block to the blockchain. These questions are difficult to answer without a large public deployment, which is one reason we have been moving forward with a rollout model that will start with large deposits and gradually reduce the barrier to staking over time.

Over the last three weeks we have been considering an interesting proposal — a suggestion on re-using the existing ATR mechanism to replace these secondary data-structures. We are sharing this proposal first and foremost because we believe it is important and potentially a significant improvement to our existing approach. We also value discussion of Saito Consensus and believe this is worth sharing publicly as it delivers some fascinating properties to Saito almost as an afterthought. Among the benefits:

For more details we encourage everyone to read the full implementation proposal. At the moment, our core team is leaning positive on this proposal and is evaluating it (read: mulling it over). We obviously expect to think about this more before committing any changes to code, but want to share these ideas publicly so that everyone in the community can help digest the ideas. Our experience is that when developers are tasked with implementing features, the default approach tends to embracing complexity. It is usually harder to conceptualize a simple idea than add complexity, but simple ideas often require the most thought.

On a closing note, we are specifically indebted to @brickblockcube for digging into the fundamentals of Saito and — when challenged with a difficult problem as part of a private discussion — thinking through the matter and coming back and provoking us with what is in retrospect a somewhat obvious question, “if we are able to take payments from the ATR transactions looping around the chain, why can’t we issue payments to them as well?” We’re not sure @brickblockcube had this exact mechanism in mind when he asked the question, but we wouldn’t be considering this approach if not for his active engagement.

The post Saito Implementation Proposal #1 – Simplified Staking appeared first on Saito.

To report an issue please email us at bugs@saito.io and let us know roughly what issue you have found. Our team will review your report and determine whether you are describing a critical issue covered under this program. If your report is considered in-scope, we will reply accepting the issue at which point you will be asked for more information, possibly including instructions on how to replicate the problem.

At the moment, our focus is on problems which are able to compromise the user’s in-browser wallet. We plan to expand the scope of this program over time, but at the moment issues that merely cause applications to “break” in reasonably trivial ways will not be considered in-scope.

The post The Saito Bug Bounty Program appeared first on Saito.

Join us for the 7th Saito Community Town Hall 7. We’ll have loads of updates, answer questions and, likely, cats!

The post Saito Community Town Hall 7 appeared first on Saito.

In the meantime, check out this animation from our new ELI5 video to get a sense of what is coming. This snippet is from a video introduction that will be displayed on our splash-page. We’ve worked on these animations scene-by-scene and are pleased with the work everyone is doing to get things right.

These kinds of glossy “show off” graphics are matched by simple animations that help deliver the Saito message. This is one of the animations that explains the difference between the network economics in “Saito” and “Non-Saito” networks: you can click on the button to switch animation modes:

Should we push up the website drop date? We thought about this and decided it is better to wait. Some content like our history of blog posts are still being ported and tagged and we don’t want it to drop them offline. More importantly, mobile users will notice little things like animations not being mobile-optimised. Our stats show a majority of the people who hit our website now are visiting on mobile devices especially when we push news and updates, so this is important.

We’re expecting to be able to generate a new wave of inbound traffic and interest in Saito once we have our new site up, so don’t want to waste the opportunity to make a good impression. As we wait for this to be finished, hopefully this post makes our communications strategy clearer. Our aim is a visually slick front-end + blog supported by a text-heavy and community-editable wiki/repository. We shrink from having the 3-4 major sites to a more manageable two that are easier to maintain and update.

So that’s what’s happening behind the scenes. We will keep everyone updated on the site as we move forward. In the meantime, we’re working on some extra polish to our latest game — which is getting pushed to production this week. We look forward to getting this stuff released and have thanks as always for everyone who is helping contribute by sharing word and educating in the crypto space.

The post Website Update – 2022-04-11 appeared first on Saito.

Despite this, we are delighted to announce that we have removed the last project provided liquidity from the BUSD/SAITO pair on Pancakeswap.

This means all revenue from liquidity provision on Pancakeswap is going directly to community members. We are grateful to everyone in the community who has stepped-up and supported SAITO this way and think the occasion is worth celebrating.

Many cryptocurrency projects create artificial rewards by dumping tokens into pools and handing them to “stakers”. At Saito we believe this lessens the value of tokens by inflating the token supply and makes it harder for the market to properly value an open network.

As outlined in our PancakeSwap Liquidity Program, we are committed to re-adding liquidity should the amount provided by our community fall. In the meantime in answer to the Telegram group favourite: “wen staking:” we are happy to note that the APY for liquidity providers on the Pancakeswap pair is currently 200%.

The post Community Take-over: Pancakeswap Liquidity Program Update appeared first on Saito.

General update

• The Ultimate Saitozen campaign successfully concluded, and winners should’ve received their prizes by this point.
• In the time from the previous Town Hall, the Saito community has seen explosive growth.
• The Building Web3 event hosted by the Saito Network was a resounding success.
• SAITO has been listed on Sifchain
• The Saito team secured a partnership with Anyswap, in which they have provided a bridge to move Saito tokens from Ethereum into the BSC.
• *The team has continuously been looking into the best ways to make it easy for the community to obtain Saito as well as reward them for holding (via liquidity pools, farms, etc.) while steering clear from shitcoinery that would dilute value (such as airdrops).
• The third vesting period concluded without issue; the Team has connected with our supporters to find the best ways to promote Saito.
• The second and final milestone for the web3 grant has been submitted.
• Two new developers have joined the Team.
• A new game, Wuziqi, was added to the Arcade. It was developed by Richard and his son to showcase how easy it is to develop apps, Saito.

Tech update

• As the second milestone of the web3 grant has been delivered, the team is now working on strategies to integrate with the Polkadot ecosystem.
• Rust continues to move forward; networking still needs to be completed.
• The In-Browser JavaScript version has been upgraded to keep up with the improvements on the Rust version.
• Improvements from the Web3 milestones and the Rust client have improved the gaming experience and organic traffic for the gaming aspect is picking up.
• Two new games were hinted at in the works.

Questions

Raja: The current circulating supply is much smaller than the max supply. At what time will supply be increased?

David: The token distribution and supply are the way they are because of the way the IDO had to be handled with Polkastarter, that community expects that kind of breakdown. That doesn’t mean we know for sure what exactly we are going to be doing with the 70% that’s allocated, we’ve got rough carve downs, we don’t even know necessarily if these tokens are going to be released. What we don’t want to do, however, is commit to a public strategy for releasing them that is counterproductive to the goals of what we’re doing. That might be something like a really bad pay-to-play strategy, where you buy traffic, and you buy a two-month pump and then the tokens dump because you flooded them out to people who aren’t using the network. The roadmap is going to talk about tokenomics but to give you a sense of what that is; we’re looking at having the token supply increase relative to usage on the network and activity, we understand that token price is something that is a really powerful marketing tool, and we think it’s important to be sensitive around that. 

I’m not sure how much more specific we can be other than there is a portion that’s the community foundation, we have no idea how we’re going to manage that, we’re hoping to work with you guys and set up some kind of foundation, it’s not something we’re dealing with yet because people approach these questions when they’re thinking about DeFi and they’re treating Saito like a DeFi thing instead of what we’ve really got, which is we’ve got the Bitcoin distribution problem but we don’t have a block reward, which it’s a challenge, but it’s also positive because I think people are beginning to realize, especially in the last two weeks, that we don’t have a block reward with extra Saito hitting the market every hour, and the activity and the interest really are being driven by the expansion of people learning about what we’re doing. 

You can expect details, the broadest picture is the faucet that we’re really interested in is the advertising faucet, we want to be bleeding tokens out to people who are using the Saito network through an advertising network, so if you’re using the Saito applications and you install an advertising module, you are now slowly getting tokens in because we’re showing you ads. Ideally, we can spin that off onto a separate company or get someone who’s not the core team to independently manage that but for that to work, we need to get the applications and the usability to the point that people are actually coming and that’s why we’re particularly happy with the organic growth and we’re looking at this stuff.

I think the people that are really concerned about this are coming from a DeFi background and they don’t know what we’re doing and they’re new to the project and they’re like “hey, is there a rug pull coming?”. Six months ago, we got a lot of that on the night of the IDO and there were questions because Saito was just a token people didn’t understand. The important thing is that we get the circulating supply and the distribution strategy in tandem with the growth strategy so that it pushes the network instead of crippling it. We’re not interested in committing to something we don’t need to unless we know that it’s rocket fuel behind us, all of us. I will say focusing on that short term might not be productive because token persistence needs to be there for every token in really small amounts before people should be worried about anything like that and we’ve still got time to go before that.

Trevor: The Saito BEP20 token contract is from Anyswap and not the Saito team, are you guys releasing a BEP20 Saito later or will you use the one from Anyswap at BSC?

Richard: This is a really important question and the first thing we’ve had to do is make absolutely sure that the Anyswap contract is secure enough to be involved with it. We’re happy on that account but we’re still treading carefully because of these exact questions. Our biggest concern here is it suitable for the community? are we putting people at any risk are we exposing them to any situations that aren’t good for them? and that relays into what’s good for the project, so we have no objection to locking up some of the ERC20 Saito as a BEP20 Saito of our own contract making if that’s going to help people.

Our next step is to survey folks set some thresholds for how much Saito we want wrapped on the BSC chain before we think it’s worth putting project time and resources into pursuing something there because I don’t think anyone on the project wants us doing a big effort to get something to happen and then it’s not serving any big purpose for the community or the project. So obviously usability and safety, security first then is it a need that the community has? and we have to balance that with obviously the core dev and those sorts of things but also with looking at centralized exchanges if that’s more suitable for people and other partnerships. So, no objection to a BEP20 Saito token, obviously we have a completely secure smart contract, we could do that with that we’ve already used for the ERC20 but that’s time and resources and execution we don’t want to necessarily deploy until we know it’s going to help enough people to make it worthwhile.

George: Token permanence wen? Rust wen? Staking wen?

David: We need to get this Rust out and Saito-lite Rust, it’s a private repository now, so once they’re live and they’re capable of supporting, we need to throw them at each other, we’re going to need a bit of time to make sure that they’re not imploding and then when they’re smooth enough we need to be able to migrate the Arcade and the transaction volume onto the new software client. I don’t know how long this takes, bear in mind we’re onboarding new developers at the same time we’re probably going to be dealing with refactors of various components at various times, what we’re looking at is bringing the token permanence on basically the same way that Kusama kind of does it with reaping. You guys can think about it let us know what you think, because this is a useful thing for us to be talking with you about. The idea is that we will be guaranteeing token balances on the network at a kind of falling level, so someone who has a big balance in the staking mechanism; if the network gets reset we will guarantee that those tokens are there when it’s reset but we don’t need to worry about someone who has like a 5 Saito token balance, so that kind of stuff doesn’t need to slow us down, and what we’re looking at is we’re trying to figure out does this work? how does it work with things like the token release schedule? and when we can be saying look we’re going to be guaranteeing various levels and how quickly it falls so that’s the general approach and I think the dates get fuzzier the further out we go.

Richard: That’s one of the things you can say, kind of like quantum physics, the more definitely you give a date in software development the more you have to pad it for security and you’re still at risk of overrunning it because software development requires the iterative working towards the point and you discover things along the way, that’s just the way it is, so what we are most keen on doing first is getting the messaging out there, what the stages are and as much information as we can about timing on those as we can, letting people know what targets are, etc. We want to be as open and transparent as possible, but we need to be careful with messaging because things get away from you as soon as you say something in this field.

For those who missed the live meeting, you can view the town hall recording here.

For more updates, please  follow Saito Network’s official social media pages:

Twitter: https://twitter.com/SaitoOfficial

Telegram: https://t.me/SaitoIOann

Blog: https://org.saito.tech/blog

Discord: https://discord.com/invite/HjTFh9Tfec

Reddit: https://www.reddit.com/r/SaitoIO/

Youtube: https://www.youtube.com/channel/UCRUhZVAUH4JyWUFmxm5P6dQ

The post Saito Community Town Hall #4 Highlights and Recap appeared first on Saito.

General Update

• The Ultimate Saitozen campaign has been launched to explore different approaches to take when generating community and engagement beyond giveaways.
• The Ambassador program continues to roll out, a few quality people (particularly from the community) have been brought onboard. We want to extend an invitation to people who want to represent Saito independently and talk more broadly to the community and would like assistance to do it.
• DOT arcade has been out for a month and work is being done on generic crypto support so that more tokens can be easily incorporated with Saito as the underpinning layer.
• There was collaboration with StackOS (The Ultimate Saitozen is running on their infrastructure)
• Saito’s ramping up hiring, new positions are being open at https://org.saito.tech/jobs/ If you or anyone you know is interested in taking part of the future of blockchain please let us know

Tech Update

• Work is currently being done to move from Saito Classic (a basic implementation of a single node, with routing work and a golden ticket every block) towards adding the pieces the production network needs, the biggest three being:
  • Automatic Transaction Rebroadcasting
  • Networking: Saito nodes now have fully binary channels, as opposed to JSON
  • Staking Mechanism is being put in place
• Rust Client progress is still on timeline and is expected to be done in two months and a half.
• Once the Rust Client is completed a new updated Roadmap will be released detailing what comes next, including things like Token Persistence.

Questions Section

Sergeant Saito: What are the possibilities of a Saito mobile app?

David: It’s a question of whether we are prioritizing when Rust is on the network and what our priorities strategically be. We can do a lot of this stuff, but if we are doing that, we are not doing something else.

Richard: One of the things to look forward for the Saitoverse if for third party developers getting involved and putting out their own apps. We’ve built mobile wallets before, and we think this is something that will either come organically through partnership or will be something we’ll prioritize when it becomes the best thing for growing an userbase and community.

Globalnode: Regarding Marketing/Promotion of SAITO, and the pending release of the full protocol. What’s the strategy of hiring internal marketing team member versus a PR firm or team to handle independently, potential larger reach and increased efficiency?

Richard: We are building a base capacity now, we need to make sure we have the ability to execute things ourselves or to instruct and work with a firm, where we need to, in a way that honors what the project is about and that’s effective. An example would be what we are doing with the Ultimate Saitozen, we need to find out the kind of fun outreach that gets any traction. What works for us and what doesn’t so that we can then start measuring metrics, etc. We don’t want to blindly spend tokens, because spending tokens means more whales, we can get more investors, but they are going to be dumping at some point.

Without throwing cash around in a silly way, how can we find out what’s worth spending money on that has a net positive effect in terms of getting the word out. In that sense, as a project rather than a company, I don’t think a large PR engine sits that comfortable inside the project so we might be more likely to use different thing and we might also be more likely to look to much more community-based ways of doing things organically.

David: What I see is that most of the PR firms in the space treat your token like a shitcoin and don’t focus on the fundamental value question. I would be open to hiring one, the challenge is that it’s hard to get people that understand Saito. I don’t think our growth strategy we can throw at a PR firm, what I’m hoping is that by generically adding support for cryptos much more easily, when that is rolled it will be a lot easier for people to understand the value of Saito because it will connect with third party cryptos in a tangible way. I’m hoping that the narrative that we have will get better moving forward and that will allow PR firms to understand us more easily. I don’t think we should do it for another two to three months because I think that the stuff we are talking about will happen by then.

Globalnode: Regarding UI/XD, what strategy is being implemented for the roll out of 2022 level web3 experience, with all the graphic bling, and usability requirements needed to put the SAITO NETWORK in the best possible light/position in the market?

David: The strategy is to make the games as best looking as we can, we bring in designers to improve on it within the structures of what they can do, and we see if integration with third party cryptos can get us promotion and integration into other crypto communities and spread that way. I personally think getting web3 cryptos integrated is more important than flashy design, but I’m perfectly comfortable with us hiring for graphic bling as well.

Richard: We should remember that the Arcade is principally a showcase to show what the network can do. The game stuff developed out of us asking ourselves “How do we get enough traffic?”, people doing real things in the network to test it and stress it. We got to be very careful about over polishing things, since that makes people think that’s the product. On the other hand, if it’s not polished enough, people don’t spend time with it, and we don’t get the usage and testing we need. Particularly with the Rust backbone and nodes running on Rust, with the extra capacity we get out of it, stressing them is going to be really hard.

David: We can get someone to redesign the site so that it looks better, but if they start touching the Arcade and the applications, then suddenly, we got more tech work that hits us. We are punching on this right now until Rust and web3 crypto integration are done because at that point we think we’ll have a better onboarding flow for people.

Greenweeny: Curious about what brought the team to Beijing? Any particular reason for choosing that city as your HQ?

Richard: David and I came to China before crypto. We met through the Bitcoin community in Beijing, so in a way we owe a lot to the community here, especially in the early days when it was pretty insane and cool. Right now, David is Thailand, some of the team is still in Beijing, but we are not operating in China. We are not a Chinese company; we are an international project.

Finesto: With so much exposure to China, how will Chinese regulation negatively affect Saito?

Richard: China’s regulations have the same impact on us as it does on other projects in that impacts Chinese users and what they can do. We are not DeFi or shitcoining like crazy, so we are not doing anything that the regulation is aimed at curtailing. For us, the impact has been mostly what the regulations have done to markets and people’s general attitudes in the industry rather than impacting us specifically as a project. Yes, we should be aware, as anyone that is here, and be very attentive to what the authorities are doing and the regulations, etc. but we are quite confident that’s not an issue.

Biko: This will be a very broad and open question, but what’s your main concerns about Saito? In the sense of development, tech, marketing, everything considering Saito. I can’t name a lot because I don’t understand the tech on such a profound level, hence my question to you!

David: for me, it’s that we are really struggling to get people to understand. We can explain the problem in a straightforward way, but because of the way the industry is, they don’t care. They don’t care about their blockchains having these problems, they are not interested in making solutions and that puts a greater burden on us. We can deal with it, but in means in some ways we have a longer roadmap because we need to make these things ourselves.

When people understand, they get very enthusiastic. You can see it with the people that have stuck around and really dug into the ideas over the last 3 or 4 there has been a realization of how people don’t understand these problems. It’s great for to see people coming around to our way of looking at things and acknowledging these are real problems.

Markus: Do you have any idea when I’d be able provide a Saito node? I’d love to play around with it. Also, is it theoretically possible to build my own JS Saito app?

David: You can run a Saito right now and you can build apps on it. If you don’t know how to do it, send an email to me at david@saito.tech and we’ll walk you through it. If anyone’s interested in this, let me know what you want to develop, because you can build and deploy and depending on what you want to build, we might be able to help as well.

For those who missed the live meeting, you can view the town hall recording here.

For more updates, please  follow Saito Network’s official social media pages:

Twitter: https://twitter.com/SaitoOfficial

Telegram: https://t.me/SaitoIOann

Blog: https://org.saito.tech/blog

Discord: https://discord.com/invite/HjTFh9Tfec

Reddit: https://www.reddit.com/r/SaitoIO/

Youtube: https://www.youtube.com/channel/UCRUhZVAUH4JyWUFmxm5P6dQ

The post Saito Community Town Hall # 3 Highlights and Recap appeared first on Saito.

Check out the full transcript below.

Richard: Thanks for joining everyone, great to have you all here. The format for today will be a quick update from me on some kind of general stuff quick tech update from David, then a new kind of feature just introduce someone from the team which will be Clay, and then we’ll get on to the real purpose of the of the Town Hall which is open question format, you know, letting people dig into the project, find out things they don’t know.

There are some questions already in telegram and I’d really encourage people to drop questions into the chat so we can get a sense of what people are wanting to know and so we can kind of flip between different people on our side make sure it’s not me droning on or David getting most of the words in. So, kicking all of that off just a kind of quick update on where we’re at; on the marketing side the first thing I’d say is I hope you’re seeing more of the project around and about, we’re really trying to expand what we’re doing in the marketing space. Some of that includes more of things you would have seen before and some of that is experimenting trying new things some really great stuff come out of community as well, like the guys putting together the voice the citizen voice, just sort of recapping and bundling up some of the great stuff that’s happening in community and making that available and digestible to people. We’ve also done some stuff I kind of think of as flag waving type marketing, you know, it’s not so in-depth but it’s just getting our brand and our name out there, trying to pick up new people and let them see that we’re there and hopefully pick up some of them as a sort of converts and we’ve seen that with kind of twitter competitions and the arcade photo competition. We’re just really trialing stuff there and seeing what works and what gets some traction for us.

We’ve also been trying some new stuff around dot arcade, just trying to push into Polkadot communities etc. Again, you know we’re trying to sort of make sure we get our voice out more broadly than we have before and to different communities and things and anyone who’s got any ideas of ways we can reach out better to community there we’d really encourage them you know hit us up in telegram make suggestions we really love that.

And then the last probably biggest thing that’s happening as well is that we’ve started working with some new people in the ambassador program, so we’ve been uh advertising that for a week or so, we’ve got some people who’ve come in, most of those people are from our community, they’re not totally  new, and they’re involved in other parts of the crypto space or forums like reddit etc., and we’re working with them to help them get that Saito message out more organically and into deeper into groups where it’s hard to enter as a stranger and jump in.

So that’s really a broad update on marketing and we’ll be able to answer any questions in more depth later in in the main section. Before we move on to text some quick project updates, one is we got listed on ZT so it’s always good to have another exchange and we hope that keeps up for the next while, other just big functional news; the second tranche, what there was of it that hadn’t gone out already of the seed and private investment round tokens, went out about a week and a half ago, that wasn’t too much to go out and went out without an issue so it’s a while before there’s any more token release and on that note we um have made some updates on medium and on our blog if anyone’s interested in details and we will be moving basically all of the treasury tokens to gnosis vaults in the next few days; we’ll have announcement about that, and that’s really just a security measure particularly now that we’ve well and clear that second charge and bettered in what our spending and things are around the raise money as well, so the only thing really to note there is you’ll see an announcement about that just to be completely clear to community about what’s going on with treasury movements because people should know that

So that’s a quick update on the project announcements and then I’ll just kick over to David for a quick tech update.

David: I’ll keep this really short and if people have specific questions, we can talk about them. As people know we’re in the middle of a bunch of stuff the big thing is the Rust implementation, you guys will hear from Clay in a bit, he’s done a lot of work with this. If you’ve noticed the username registration is working a lot better now than it used to, he also had a bunch of pain on that.

Richard: We just throw the bugs at Clay.

David: Yeah, he gets the unpleasant ones. But yeah, we’re about halfway done. We started working  on networking which means getting multiple nodes connecting and we’re moving beyond the classic implementation of just a golden ticket paying a miner in router and we’re moving towards the golden ticket now paying multiple routers kind of cascading backwards, so there are a couple of big things that need to happen um and but you know we’re on schedule, I think is the important thing and anyone who’s got questions, you can fire them off or just follow what’s happening on GitHub.

Richard: by popular demand from community wanting to see someone that’s not me and David talking to them occasionally, we thought we’d introduce you to someone new in the team this Town Hall and that’s Clay; so I asked clay to just sort of quickly introduce himself and then again the point of this meeting is more for questions later so we’ll get around to those as soon as we can.

Clay: Hi everybody, so my name is Clay, like Richard said, I’ve been on team Saito for I think over nine months now. Prior I studied electrical engineering in school, and I have about 15 years of software development experience. I’ve done a little bit of everything, mostly web stuff but prior to becoming more blockchain entrepreneurial I was at google protecting their ads ecosystem on a team internally called Ad Spam externally called Ad Traffic Quality, where we basically have to detect all the fake clicks on all of Google’s ad products, so that was a lot of responsibilities. It was a cool experience and I learned a lot; it was like big data ML sort of stuff, but after that I got really into uh blockchain and surprisingly at google there were very, very few opportunities to get into that space, so I had a startup with a partner here in China where we were trying to do a platform like turnkey solution for enterprises to enter the blockchain space trying to target rewards programs and things like that and we ended up going separate ways because there was a disconnect between me and my partner and one of the big problems we ran into was actually technical. We couldn’t, the things that my partner wanted to do, I kept trying to explain to him you just can’t do that on Ethereum, I felt like we were selling something that we didn’t really have and so  while i was doing that I ended up running into David in a WeChat chat group and we were arguing about something about bitcoin and bitcoin cash I think I bucketed him as a BSV guy initially because he was some principled arguments about bitcoin cash and most of people that were  trying to speak in that sphere at the time were, there was a big disconnect between the bitcoin cash and the BSV people so we ended up meeting for a pint here in Beijing and David talked to me for like an hour and a half about Saito while the rest of the team were being more normal.

David: one lesson there is that Saito a lot easier if you have beer.

Clay: Yeah [laughter]. So at that point I was still stuck in my in my other partnership but I knew at that point that if I ever was able to exit that and looking for something cool to work on in Beijing that Saito would have to be it, so as soon as I was available I joined the team and it’s been a great experience so far, we’re really doing cool stuff here so it’s great. So yeah, happy to answer questions if people have them.

Richard: I see one question here from someone saying you know they’d love to see us talk more about these 51 attacks, etc.

I’m actually seeing the telegram group, there’s news of a big 51 attack today but I haven’t actually followed it today, I’m a bit busy preparing for this and other things, so I’m not sure if anyone could give us more information on that but I do think that that’s one of the things that does present us with chances to talk about you know what is different about Saito out there.

Clay: that’s very interesting, I’m curious what are these 51 attacks that are happening because we should know more about the space but we’re just building Saito all the time, so we don’t always know.

David: someone’s gunning for BSB so they just keep reorganizing whatever TAAL does, it’s actually kind of funny

Richard: is that what’s happening?

David: yeah, it’s just a hash attack and all of the miners are now leaving, so anyone who’s not TAAL is now fleeing for the door which makes the attacks easier so, it’ll be interesting to see what happens.

David E: Clay, where did you learn rust?

Clay: So I had a quite a bit of experience, I had once upon a time done a game platform in C with embedded Python and I learned a lot of systems programming doing that and then obviously at Google everything’s very low level you’re dealing with pushing bytes around but I did not know Rust prior to joining Saito and Richard and David were keen on using that so I’ve just spent some time up at Saito learning it here but, you know, once you know enough languages it’s easier. I mean Rust is very unique and there is a steep learning curve, but I love it, i think it’s a great. I mean, it’s by far my favorite language now. I think it’s just so cool.

David: it’s got the most helpful debugger, you know?

Greeny: I’m sorry if you’ve answered this question in the past, but why did you all choose Rust over other languages?

David: JavaScript runs in the browser, right? but it’s using one CPU and what that means is that as the block gets bigger and there’s more and more work to be done, more and more cryptographic stuff to be done, you get a limit on how fast you can process a block because you’ve got one CPU to do it.

You can optimize and trick your way around it by doing things like taking that block dividing it into 10 chunks, sending it to 10 processors and then they do their own stuff, the problem is that there are all these trade-offs that you can’t avoid. Rust is so beautiful because on a fundamental level it’s designed so it’s really easy for us to do something like read the block into memory and then it sits in that space of memory and we go to like 10 CPUs, 20 CPUs ,40 or 60 CPUs and we say each of you guys take some of this work and do it. So Rust is much, much better for parallelization and that’s really great because as blocks get huge you start to hit bottlenecks reading them into memory and moving just that size of data around and we don’t want to be doing that multiple times. I think we’ve shared some numbers; we can share some more, but basically Rust is outperforming my expectations of how fast we can get things. I think Clay’s comments as well play like mine and he’s blown away

Clay: I think the only other reasonable choice would maybe be Go, but the simplest answer is we want to get a low level language, we want to get something that’s compiled and where we’re doing real systems level stuff and we can push bytes around to really just squeeze out every bit of performance from the machine and as far as like Rust versus C++ or Go would it’s just a bit of a subjective choice but one that i definitely agree with just because Rust really lets you do low level stuff but without a lot of the sacrifices you would have to deal with C or C++ at least. I don’t know Go so well but it’s just a really great choice because it gives you the best of both worlds, I feel like we’re able to be really productive, almost as productive as you would be in JavaScript as far as just getting the functionality down but then it’s like 40 times more performance if you’re going to use 40 CPUs.

Emilio: how is the dot arcade different from the regular arcade?

Richard: One way to answer that is it really isn’t. The reason I’m saying that is the point is that it’s demonstration of being able to simply develop In Saito and then use code that you’ve written in regular standard web format to do things with other cryptos is a lot of work doing in other ways. So, the idea is really that it demonstrates how simply that you can slot other cryptos into the into the Saito ecosystem. The difference is right now it’s supporting Polkadot ecosystem tokens and in future we hope to expand that a lot more.

David: I’d just add that the um it’s really milestone one of that grant proposal that we got into the Dot people we can probably spin out milestone two anytime, I think we’re waiting to see how the outreach with the dot arcade stuff goes because partly it’s a marketing effort. You know, see how receptive that community is. One of the questions we’re thinking about post getting Saito rust up is exactly what’s the best way to make it so that we can really easily add stuff because the way we are doing things with Dot is really custom to their hardware and their servers and there are other ways that might be easier and more flexible, but yeah like Richard says is going to be pretty much the same as the normal one, the question is really when we get that second milestone in and when people can practically come with other cryptos.

TheAltz: How actively engaged are the VC investors and do they have any actual say in the direction or project or are they completely silent/hands off?

Richard: the real answer to that is it’s really varied. So we’ve got, for instance, the seed investor who is a really early supporter who’s now with a new fund that they’ve set up, that have come in again who David and I tapped for advice and investment quite on a regular basis so you know we will talk to them for advice and feedback. They have helped us find staff they have helped us structure the IDO, etc. Really daily activity, we’ve got other investors who have put some marketing muscle and things like that behind us and help amplify our messages and we’ve got others that really are very much silent partners and that’s something where we’re working with, is getting the most out of them, it’s a two-way street we need to push them to do it and it’s really changed, I think, in the space, we got a lot more investors in the recent rounds who are investors with something they bring to the party with whether they’ve got communities that they can message into or they help us with outreach and marketing, so yeah it really is very varied but we’re looking to get more out of all of our investors.

David: I think it’s something we’ve actually been focused on finding out for the last two to three weeks, we’ve been proactively reaching out to people and figuring out who’s helping with what sort of thing, because different kind of investors also mean different obligations to the project. Like Richard said it runs the gamut from like our lead investor in 2017, those guys are amazing, to a smaller person that might have got a smaller allocation because they run a blockchain promotion group or something, so it’s different.

Richard: yeah, we’ve been blown away by some people and we’re less impressed with others let’s say that as well.

Just looking through other questions, George George George George George George is saying that he’s considering becoming and applying to be an ambassador and I would say to anyone in the community if you’re interested in being part of that program, let us know, we’re not um expecting specific things, we want to find out what people can bring to the project and we want to work with them to make sure that’s rewarding and fun and exciting for them so seriously don’t feel like there’s some kind of threshold that maybe you don’t qualify or whatever, we’re happy to talk to people and it’s not wasting our time or something you can’t do, if you’re if you’re already participating in Telegram, that’s great.

Pawel: How Saito will revolutionize ecommerce?

Richard: I think the whole purpose behind Saito and the core idea of web3 is to get away from various technical and financial systems that allow incumbents to monopolize and to control what users or consumers can do. What we’re hoping to do is be part of doing that, letting people use keys online to be their identity and to own and maintain their identity and not have to give that away to the credit card company or to Amazon to be controlled on their behalf, so we’re hoping that we will see things like open marketplaces and I think that will start with things like content aggregation and stuff like that where people use site tools built on Saito to use crypto and micro payments and other things to share revenue with producers directly and other people like aggregators who are doing something useful for them rather than it being Spotify, google music maybe, one or two other services and you just have to hand over everything to them and that’s what you’ve got.

Thanks everyone for giving us your time this evening for being part of this it’s been great fun and we really appreciate everyone’s coming in and being part of it tonight.

For more updates, please follow Saito Network’s official social media pages:
Twitter: https://twitter.com/SaitoOfficial
Telegram: https://t.me/SaitoIOann
Blog: https://org.saito.tech/blog
Discord: https://discord.com/invite/HjTFh9Tfec
Reddit: https://www.reddit.com/r/SaitoIO/
Youtube: https://www.youtube.com/channel/UCRUhZVAUH4JyWUFmxm5P6dQ

The post SAITO Community Town Hall # 2 Highlights and Recap appeared first on Saito.