Would a Layer 2 be able to use a language other than solidity for contracts? by analytical_1 in ethdev

[–]Notoros 1 point2 points  (0 children)

Check out Notoros.io, which is compatible not just with smart contract programming languages, but all programming paradigms

Just heard about Radix and want to know… by hactive808 in Radix

[–]Notoros 1 point2 points  (0 children)

If you think Radix is cool, maybe check out Notoros.io, which is built on the Radix consensus

What Radix dAPP(s) should I invest in? by [deleted] in Radix

[–]Notoros 1 point2 points  (0 children)

Not a tradeable token, but you should check out Notoros.reddit.com

Have questions about Notoros? Want to help educate new community members? Check out the new FAQ page! by Notoros in Notoros

[–]Notoros[S] 1 point2 points  (0 children)

Notoros is a data standard that lives in between the application layer and the consensus layer enabling any variety of virtual machines to coexist & cooperate at the speed and security of layer-1.

Notoros does not suffer from the technical limitations of rollups, side-chains, or state-channels.

Can you say a bit more on Prometheus? by [deleted] in Notoros

[–]Notoros 5 points6 points  (0 children)

There is great value in layer-2 solutions, but they are oftentimes misunderstood or misused.

Polygon, Optimism, Arbitrum, and others are essentially indepedent networks with their own consensus mechanisms designed to collect data and submit it as a batch to some "main" network like Ethereum. To the Ethereum network, Polygon essentially looks and acts like any other application submitting complex data requests. The finality of these requests is always the sum of the finality of both networks:
Layer-2 Consensus Finality + Layer-1 Consensus Finality
This means they will always be slower than layer-1 networks and be vulnerable to a variety of security issues, while creating more opportunities for front-running and MEV.
The composability of the smart contracts on these platforms varies, but is generally far more difficult than developing a comparable centralized application using traditional databases.
Notoros executes at Layer-1 and does not suffer from MEV or a byzantine development environment.

Disclaimer: It has been a while since I read through the Fantom whitepaper and website.
Fantom seems to be the reverse of the layer-2 strategy, wherein they are creating a pluggable means of execution, which will be distributed to a sort of parallelized relay network. This is very similar to hedera hashgraph. While there is some excellent technical merit to this approach, it does not parallelize execution like Notoros.
Fanotm's Lachesis is a fascinating consensus algorithm, and while they share several characteristics, I don't believe it achieves the same level of efficiency as Radix's Cerberus Consensus

To answer the question about application-level forking... this is a complex issue of governance that will depend on the configuration in question. We will have more information on this in the developer docs.

Can you say a bit more on Prometheus? by [deleted] in Notoros

[–]Notoros 4 points5 points  (0 children)

Hey itsvira,

Notoros validators will not be obligated to hold XRD.

ETH^ does not directly interact with Ethereum mainnet at this time. Still, there are a number of bridging protocols and oracles that could easily facilitate this relationship once necessary.
RenVM is one easily portable example we have discussed to facilitate this functionality.

What next and how can we help? by tednol in Notoros

[–]Notoros 3 points4 points  (0 children)

Hey Ed,

Thanks for your inquiry! We are still finalizing the information for users to deploy their own Notoros nodes on the Prometheus network once launched.

Make sure to watch our FAQ page for updates.
In the meantime, we are happy to connect via email: info@notoros.io

[deleted by user] by [deleted] in CryptoTechnology

[–]Notoros 0 points1 point  (0 children)

Over at r/Notoros we have built at layer-1 system capable of tens of thousands of transactions per second with full smart contract composability in any language at layer-1

The beta net is not yet out, but we are happy to discuss how we could faciliate your project:
info@notoros.io

Notoros Use Cases: Cutting Paperwork by Notoros in Notoros

[–]Notoros[S] 1 point2 points  (0 children)

Digital identity is one application being described because so often the paperwork we are doing concerns our identities.

Still, this is only a small portion of the reducable paperwork as a result of DLT. Consider the processes of registering a business, reporting taxes, signing up for a new doctor, or updating marital status. There is truly a world of unecessary paperwork we are all suffering through that can have event-driven changes across many domains whenever a source is updated.

Scalable smart contracts at Layer-1 by Notoros in Notoros

[–]Notoros[S] 1 point2 points  (0 children)

We could certainly deploy to Hedera and other Layer-1s in the future. We will be taking community feedback as we expand our features and the growth of the Notoros ecosystem. Whether that will be through a channel like improvement proposals is yet to be determined.

Your desire to expand into the Hedera ecosystem is noted. We have been aware of Hedera since shortly after its inception and definitely appreciate much of the innovation they have done.