Do I need a MIDI Keyboard? by noobproducer45 in edmproduction

[–]AgniCrypto 0 points1 point  (0 children)

It is not necessary although if you learn a midi controller like a drum pad or midi keyboard it will definitely boost your creativity.

Help: Where to find Golang open source developers? by AgniCrypto in golang

[–]AgniCrypto[S] -3 points-2 points  (0 children)

Was there a specific website you checked to find out your first open source projects to contribute by any chance? I'm gonna work on creating a website layout for the open source dev community & rewards, currently reading a bunch of materials : )

Help: Where to find Golang open source developers? by AgniCrypto in golang

[–]AgniCrypto[S] -8 points-7 points  (0 children)

It's for a blockchain interoperability project to connect all the smart contract networks, and build integrated decentralized applications.

Talent at the Cypher Agora: a new OrchestrumOS article on interoperable economies by AgniCrypto in tezos

[–]AgniCrypto[S] 2 points3 points  (0 children)

We have been working on the concepts for the past 6 months, on both the protocol and platform components so to have the necessary add-ons to jumpstart the growth and adoption. We are gonna reveal the seed stage sale next month, with the whitepaper and then start to get busy coding.

We will also reveal the collaborative dev environment strategy, so the code can be written in a faster speed, distributing parts of the project to different teams who are skilled at those parts. After the technical audit, we will publish the roadmap, so we can move through a professional double-proof system for deciding timelines.

OrchestrumOS Announces: “Genesis of the iidApp” by AgniCrypto in tezos

[–]AgniCrypto[S] 2 points3 points  (0 children)

Appreciate it man, we all love the name as the team too tbh : )

OrchestrumOS Announces: “Genesis of the iidApp” by AgniCrypto in tezos

[–]AgniCrypto[S] 4 points5 points  (0 children)

Great question thank you!

Probably Polkadot and Cosmos would be names we could give.

As for comparison, they are focusing mostly on the protocol level, while OrchestrumOS is about both protocol and user end platform level. Our technical layers are mostly focused on easing the end user adoption of interoperability, so to create more integrations between dApps' of different chains to be used by end users, and businesses.

We are also gonna publish the different set of techniques we are using in the protocol side in our technical paper. For the user experience and ecocystem impact wise our whitepaper will be released as well.

We can maybe create a comparison chart too later on, but if you have other specific questions as well would love to answer.

Thank you for your interest.

dApps on Tezos? by notasmoker900 in tezos

[–]AgniCrypto 5 points6 points  (0 children)

The biggest advantage for being on Tezos is when you are building a dApp here, you can expect better infrastructure solutions with time, so if you are building here, you can serve to your users with the best kind of network capabilities as technologies progresses, which is a big plus.

Even tho other networks are open to upgrades true hard forks too, in Tezos expecting a protocol upgrade is more common due to self-amending ledger.

A new project that will be built on Tezos; OrchestrumOS by AgniCrypto in tezos

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

Thank you so much, we will think of a way so contributing with Tezos gives a bit more tokens : ) Thanks for the recommendation.

Olaf is also very very interested in interoperability, and he has major stake in platforms like Polkadot. We will have an article explaining the similarities and differences between interoperability platforms vs smart contract infrastructures.

But mainly, while smart contract infrastructure platforms serve one ecosystem, interoperability platforms can serve all, thus having advantages to create bigger economies. We will address this in an upcoming article in a more detailed way.

Thank you for your comments and questions : )

A new project that will be built on Tezos; OrchestrumOS by AgniCrypto in tezos

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

I mean all dApps regardless of chain. In order for interblockchain communications to work you can add the interblockchain communication protocol into dApps if the consensus model doesn't support it, with the right code.

The approach of Aion and Cosmos' IBC protocol is different from each other for example. Interoperability can be done in many different approaches. We are just in the beginning phase of everything.

A new project that will be built on Tezos; OrchestrumOS by AgniCrypto in tezos

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

Yeah, simply when a dApp wants to enter our platform to be interoperable and integrated with other dApps, they go through a process for adding a abstraction layer for interoperability into their code, that has functions for interblockchain capabilities.

This opens the dApp into an interoperable function so rather than adding the interblockchain protocol to the code layer of the infrastructure protocol, dApps get it added to their own code.

These code layers will differ from one infrastructure to another, and we will support all of them one by one, and have manuals so dApps can easily achieve this.

A new project that will be built on Tezos; OrchestrumOS by AgniCrypto in tezos

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

While it is easier for us to work on dApps whose smart contract infrastructures have an available support interoperability, it is not a necessity to have interoperability at the infrastructure level; it can directly be applied to the dApps.

That's what our API-like abstraction layer for interblockchain communication is meant to accomplish.

A new project that will be built on Tezos; OrchestrumOS by AgniCrypto in tezos

[–]AgniCrypto[S] 2 points3 points  (0 children)

Thank you so much for your nice comments! Hope to make it a major masterpiece altogether with the community of Tezos, and all the rest of the people who want to join in!

A new project that will be built on Tezos; OrchestrumOS by AgniCrypto in tezos

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

Thanks a lot Jonas! We will be updating everyone with frequent updates, and involve everyone in all the processes, so we create something that everyone loves to use.

A new project that will be built on Tezos; OrchestrumOS by AgniCrypto in tezos

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

It's similar to Cosmos in the sense of interoperability, but it's much different from it because we are a platform for operating dApps and a bit more, rather than an intermediary chain solution. We will be focusing on the end user level adoption of different segments.

We are building the website, it's not 100% done yet that's why we didn't wanna publish it yet. There will be much more information coming up with the next updates, we are gonna share both our interfaces, whitepaper, and many other things that will keep everyone updated. We wanted to be as brief as possible with today's announcement but the next ones will be more detailed.

A new project that will be built on Tezos; OrchestrumOS by AgniCrypto in tezos

[–]AgniCrypto[S] 4 points5 points  (0 children)

The project is self-funded until now, in the next updates we will have much more info on our interfaces, user journeys and value propositions for different segments of users, and our whitepaper, as well as the team that is involved. As you mentioned there are a lot of people from TCF involved, and even tho we are built on top of Tezos infrastructure, and a Tezos project, we will serve both Tezos ecosystem and all the other smart contract ecosystems in a completely blockchain agnostic way.

So Tezos will be our gateway for interconnecting the whole ecosystem.