nOS Report #2 — Pre-sale Requirements, Platform Updates, NEO Europe Tour
Ever since we announced the nOS pre-sale requirements last week, our community (which is now over 50,000 strong in just 2 weeks!) raised some questions about participating in the pre-sale.
Let’s talk about that, plus the NEO Europe Tour and this week’s nOS platform updates.
Join our newsletter at https://nos.io to receive our updates by e-mail.
Pre-sale Requirements
Last week we published our public pre-sale requirements:
Only contributors to the nOS codebase and teams/developers building a dApp on nOS will qualify for the public pre-sale, unless otherwise stated.
nOS dApps that are submitted for pre-sale access are required to have a repository on GitHub with a reviewable commit history.
All project code must be under the MIT License.
Active Discord participation is required.
nOS pre-sale FAQ
Note: These details are about the pre-sale. The public sale will require no special efforts other than standard procedures (such as KYC/AML) unless otherwise stated.
1. How do I find a project or team members?
We have a nOS Networking Megathread in the /r/nOSplatform subreddit. Comment in that thread using the template given in the OP to find team members!
2. Can non-developers qualify for pre-sale?
Yes. If you’re not a developer, you can join or create a team. There are plenty of people looking for a development team in the nOS Discord.
Developers must upload their code (including commit history) on Github.
Non-developers in a team must log their progress and contributions using Github Gists. You can share these contributions frequently (such as once per week) on the nOS #develop Discord channel.
Only team members with significant contributions to a dApp will be taken into consideration for the public pre-sale.
Be productive and descriptive. Users contributing a single line of code, or a gist solely describing “Various business input.” will not be taken into consideration.
3. What nOS codebase contributions will qualify me for pre-sale access?
Important: To qualify through codebase contributions, you must follow the nOS Contribution Guidelines.
You can contribute to Github issues created by the core team with the “Community Issue” tag. After successful review of your GitHub Pull Request, and your contribution is merged into a branch, your contribution will count as valid.
If you wish to make a contribution which is not listed as an existing issue:
Create your own issue and apply for the “Community Issue” tag by contacting the nOS team in the nOS Discord #develop channel.
4. What’s the deadline for dApp submissions?
This will be announced 1–2 weeks prior to the actual deadline.
You have at least until May 31st. Best time to start is now!
5. If I start building a dApp now, could I qualify for the pre-sale?
Yes.
If you have any questions, feel free to contact us on the nOS Discord.
Europe Tour
nOS Founder & CEO Dean van Dugteren attended the NEO Europe Tour to present the nOS vision, and give NEO & nOS dApp creation workshops.
Madrid
Paris
Vienna
Zurich
Platform Updates
Github Community Issues & Guidelines
The “Community Issue” label means the issue is open to be handled by community members. Successful contributions may result in access to the nOS public pre-sale.
We welcome contributions to the nOS code base. If you are interested in becoming a contributor, please read the contributing guide that covers the following:
nOS API npm package
https://www.npmjs.com/package/@nosplatform/api-functions
- Released the initial public release
v0.1.2with API bindings and prop-types for React (@nosplatform/api-functions)
The nOS API npm package allows for easier development and broader implementation of the nOS Javascript libraries.
Client Feature: nOS Protocol & Resolver
https://github.com/nos/client/pull/117
- By adding a custom protocol, developers can use the built in URL class to parse queries for us.
- Support dApps referencing images, sources, and other third-party files stored via the nos protocol. (e.g.: nos://third-party-file).
- Further integration for third-party browser support. (e.g.: Users can open nos:// links from within Chrome/Firefox).
Client Feature: Transfer Funds
https://github.com/nos/client/pull/113
nOS React dApp Starter Kit
Check out the documentation of the dApp-starter-kit to get started.
Repositories:
Muon Research & Development
https://github.com/nos/client/compare/develop...muon
Muon is a development framework based on Electron that’s built by the Brave team.
We’re considering integrating with Muon as it enables some Chromium browser-specific features, such as natively supporting a core set of extensions within the nOS Client (e.g.: 1Password, Anti-ad and tracking plug-ins, and Blockchain-specific Browser Extensions).
We will continue development on Electron for the time being, and integrate with Muon in the future.
Follow nOS
Thank you for your continued support!
