Showcase — A new monthly ceremony
Showcase — A new monthly ceremony
Showcases are a monthly recurring set of presentations to create information symmetry both internally and externally.
As we ventured into 2019, one principle we’ve adopted is that of information symmetry. In the pursuit of hitting deadlines, being first to market and a relentless focus on outcomes, a natural rift occurred in 2018 between us, our partners and external contributors. As we examined this rift, it became clear that the primary drivers were too few people having access to important information that would have helped drive their decision making.
To adapt to this we’ve experimented internally with a ceremony we call the “Showcase”.
What is a Showcase
Showcases are an opportunity for Aion Foundation teams to share progress they’ve made in the previous four week period. They come prepared with talking points in a consumable group format that covers a 10 minute period (presentation, demo, etc.) In attendance are the members of the presenting “pod” and all “pod leads”.
10 min — present/demo what you’ve accomplished in the previous 4-week period, snapshot of what’s coming in the next 4 weeks.
10 min — Q/A with leads
Showcases go public
As our first few rounds of showcases have gone well and we’ve ironed out the wrinkles, now is as good a time as ever to make them public. The goal being an increase in the surface area of exposed third parties to the inner workings of the Foundation. If you know what “pods” are working on, you can adapt your efforts to help us in the problem domains we are focusing on. We will keep archived showcases in a reference section in our roadmap going forward.
Without further adieu…
Disclaimer: Some of this content are in early stages of exploration and as a result are not always commitments to outcomes. Much of the content is sourced across the Aion ecosystem and is not controlled or managed by the Aion Foundation. Not all questions have answers immediately and teams take those questions back with them. Notes are not exhaustive and are purposefully raw, it is our hope that summaries and higher fidelity highlights will be generated by those who are interested in curating this.
21 Mar, 2019 — Showcase
- Productizing docs, stripe has been a source of inspiration for this. All documentation is oriented around the problem facing the developer.
- A content tree has been created to outline what this new format looks like
- Videos has been a focus of the last four weeks, we have three formats for youtube content and learned a lot from some experiments
- We will be re-orienting ourselves over the next four weeks on video content that was a successful experiment
- New two week sprint format to groom a backlog of content both written and video, this has been a big issue for cross team collaboration
- Community notes, need to focus on some of the common questions of the community and to have more presence meetups.
- We attended the UofT hackathon and had a lot of interest by students building on the AVM. Was great for feedback on environment setup and documentation
- Sam: Productizing docs, is this common use case or common components?
- Matt: How do we stay relevant on the components?
- Sam: How do we prioritize the components we can be competitive on?
- Matt: We should be highlighting outward facing personalities. How do we get people in the community to know them?
- Accomplished milestones list included in presentation
- Current work in progress included in slides
- Current timelines for milestones upcoming leading to a MainNet hard-fork to AVM.
- List of risk and mitigations
- Test coverage
- Billing costs are high across the system
- DoS and Consensus breaking AVM bugs, all of which require creative stress testing
- Matt: Dates, April specifically is day two of conference so be aware of our capacity here.
- Ian: For the flexible date on MainNet hardfork, how do we decide this date?
- We need a schedule for migrating from mastery fork and mainnet fork in a sequence of events
- We need a set of criteria for go/no-go
- Functional comms plans for forking
- Community and Developer comms plan is separate
- Matt: Differentiating factors from us vs solidity?
- Our product launch page is a good representation of how we’re thinking about this.
- Launches from the last month included in the presentation
- UofT Hackathon
- Syna wallet mobile, web and desktop launched
- Docker images for Java and Rust to allow developer to download the kernel and use it with any OS
- Monster Chase mobile game on Aion
- IntelliJ plugin for Java contracts, testing, debugging and deploying to embedded AVM, send transactions.
- Items in flight included in the presentation
- Ian: What are we playing catch up on, and what are we “feature advanced” on when it comes to tooling and layer 2?
- All product launches should orient themselves around how they are differentiated from their competitive landscape
- Makki Wallet, is this Aion branding?
- No, Chaion branding
- How do we get these projects “launched” once complete. ie. get a large group of devs using them
- Some suggestions from the group around demo application and more.
- What’s been worked on and investigated over the past month included in the slides
- Intermediate Update Proposal for Consensus has an update confluence page. This goes over how open we are to a 51% attack. Investigation findings for a stop gap fix
- Will not work: Local Posterior Checkpoint, Too fragile, too easy to force fork of the network.
- Will not work: Delayed POW common implementation using Komodos — their implementation may incentivize cartel behavior
- Might work: POW + PoS Ticket Voting, likely gives us 10x the resilience of our existing hashpower
- Might work: Pseudo-PoS using VRF, this is potentially a net new solution we should explore more.
- Sharding and sampling updates included in the presentation
- Matt: Is there a mechanism you’re proposing to reduce the global message propagation?
- You need organizations of communication so that not everyone is talking to one another at the same time.
- Sam: For the Stop-gap proposal and implementation
- We tried to make it lean and minimize our effort.
- We wanted to involve stake, since it has better properties.
- Didn’t want to distrust how miners currently work too much
- DCred model has less changes to the software pools are running, we would only need to change payouts. Miners would get existing or more reward plus stake, which is a change in monetary policy.
- You incur a set of operational and co-ordination expenses when approaching any staking approach, user experience is very important here.
- Jeff: We need a solution like this, this year. I have a lack of confidence in sharding approaches, this may be less of an interim solution than sharding and ETH 2.0.
- Matt: How far are we from a conversation about next steps?
- Let’s get to a proposal.