One questions: Can you give us more details on how and where will the registration for betas?
I think that up to 10% via PoW be logical. No more, please.
If 70% goes to ICO and 30% to PoW where do the bounties come from?
As we said, in the distribution 0% will go for us as background/premine/developer funds/bounty funds, we believe it would be unfair. All payments will be supported by us from what we gather at ICO.
Hmmm, I'm not too sure why so many people have a problem with devs holding a share of their coin. I agree that it's hard to determine the right amount, but in the end, it gives the devs an incentive to keep working on their coin.
Here is an idea I had regarding dev shares:
There is one ICO in the beginning. The devs keep a relatively big share of the coins, but they are locked by a contract and are sold in not one big, but in multiple following COs*. When this COs will happen is determined before the first ICO, ideally, the coins are either generated at fixed block heights or are locked by smart contracts and released at fixed block heights.
My reasoning behind this is as follows:
1.: It will keep the devs invested, since successful development would increase the amounts collected in the following COs.
2.: Since the releases are fixed, the market can adjust.
(I had additional points, but I'm too tired to articulate them…)
Obviously, the amounts and points in time when those releases are happening need to be determined carefully.
Thoughts?
*Since ICO means "Initial Coin Offering", the others are just "Coin Offernings"
I think I'm with the dev at this point. It is a good decision to decide to distribute 100% of the coin, not holding anything for them. As said, they will buy stakes but when the ICO has ended. On the other hand, you and I know that is probably a big big ICO, which do not need to earn extra money as premine.
I would add that if the bounties are free (premine), only serve to be dumped into the market as soon as the coin hits the exchanges. Thus, if the devs have to buy coins for bounties in the market, at least it serves to counteract the dump of the bounties (we all know that what is obtained in signature campaigns, users are going to sell as soon as they can)
I find a question, if 100% distributed, where does the bounty coin from? Devs buy coins or they get the coins by mining??
They don't reserve one coin which is good, look DAO, but DAO had bad future, this coin will have good future.
As I have said several times, we will buy XPO for bounties.
Will this Opaircoin on full feature released once the ICO has been completed? If not how soon will all its features will be fully implemented? Do you have any working roadmap as well?
Has it done some all kind of testing too? Thanks
Hi, I can not give you a date when it will be ready all our features. As we said, the first public beta will be available two weeks after the ICO and the first stable version two months later.
About our important features that I guess is what interests you, both the implementation of smart contracts and decentralized debit cards will be present from the first beta, which anyone can test them. Obviously from day 1 will not be complete and stable, so it is a beta. The decentralized debit cards are likely to be ready for the first stable version of the platform, but not the implementation of smart contracts as it involves a higher amount of working time, knowledge and development, given the language we are using.
Very interesting project, some questions before I invest:
1) is there a minimum amount of funds you need to go on and will you provide refunds if you don't catch the target
2) have you considered how much time will it take to make a smart contract platform in a functional language? Ethereum's language is much simpler than a functional one and only the task of making a new language with 2-3 people is daunting.
3) what is the main language that this coin will be developed? c++? the gui seems same as all other wallets, it's just a prototype right?
best of luck
btw my 2 cents:
this project is much more interesting than waves BS that was a project without any real innovation, im just worried that too much is promised.
language naming proposal: laniakea (the new galaxy supercluster discovered)
Very interesting project, some questions before I invest:
1) is there a minimum amount of funds you need to go on and will you provide refunds if you don't catch the target
2) have you considered how much time will it take to make a smart contract platform in a functional language? Ethereum's language is much simpler than a functional one and only the task of making a new language with 2-3 people is daunting.
3) what is the main language that this coin will be developed? c++? the gui seems same as all other wallets, it's just a prototype right?
best of luck
btw my 2 cents:
this project is much more interesting than waves BS that was a project without any real innovation, im just worried that too much is promised.
language naming proposal: laniakea (the new galaxy supercluster discovered)
Hi,
1) to be honest we do not have a specified amount but we believe that, at least, 700 BTC would need to put together. From then on, all collected serve to optimize, accelerate, hire more people, marketing, legal costs, go to more events and create a division that works as an incubator (as we said in our thread: "When we have enough founds, we would like to use some of them to create a division that will work as an incubator to relevant projects (can be IoT related works, DAO, Dapps, frameworks and so on) in the ecosystem we aim to create in Opair.")
2) as I said above, it will be one of our priority but we take a lot of work. Obviously if we develop it with only two people would take longer than planned. There are currently 3 people on our team who can help in this regard but with the ICO funds we will expand our team.
3) for the development of Opair Core, we will use the languages we know best and we consider appropriate for that function, which are C ++, Python and C# and, of course, OCaml for the implementation of the smart contracts. We rule out the use of Java, by fluency and security problems that its use entails.
