Hello, HristianD, and glad to see you here following up. I assure you, I am not trying to create a smear campaign. The last thing I would want, is to create a bad name for Wings by creating smear campaigns against projects which utilize WingsDao for evaluating their token sale.
For those of you who do not know the post he is responding to, here is the original post.
https://bitcointalk.org/index.php?topic=1477055.msg35976973#msg35976973You say that my comments around Wings integration are baseless and that they have been answered already, and you included an article here.
https://medium.com/the-os-university-blog/faq-from-the-wings-community-3c4cb8266dddThe most important part of this blog states "Currently the tech team is working on a solution for this after weve got in contact with them. Update on this point will follow shortly."
Until an update is made regarding this situation I will not unflag this project.
There are three ways to utilize Wings, and they are as follows.
In the Beta, anyone who deposits 5000 WINGS can post a project. The beta version also allows for automated and semi-automated payments of rewards to forecasters. Note that projects can use the following methods:
1. WINGS contract generator of ERC20 token sale
This is fully automated
2. WINGS Integration (
https://github.com/wingsdao/wings-integration)
This is fully automated IF implemented correctly.
3. WINGS Light Bridge (
https://github.com/WingsDao/wings-light-bridge)
This is not fully automated; meaning the project serves as an oracle and manually fills the rewards tokens into the contract.
Method #1 is meant for projects which do not have an ICO contract already, if they do forecasters are recommended to question the project leads as to why they are planning to issue 2 tokens.
Method #2 forecasters are recommended to collaborate and read the actual smart contract(s) code to determine if the integration will work. If a contract with bad code is accepted, there is a possibility that rewards payments will not occur correctly.
Method #3 requires the forecasters to establish some form of trust with the project leads that they will carry out the requirements to resolve the forecast and make payment. This is the most risky and requires extra care and due diligence on the part of the community.
Your project, chose to follow method 1, which is fully automated, meaning, for rewards to be calculated and for Wings forecasters to receive a reward, the contract will have to go thru all of the steps, from forecasting, countdown, launch, after the sale ends, the contract will calculate rewards, and last but not least, it allows a way for forecasters to claim their rewards.
And there lies the problem. Since the current contract does not allow KYC, and since you will be implementing KYC, you will not be able to go thru the steps needed for this to be an automated process, thus, forecasters will have no way to collect rewards, and in fact, rewards cannot even be calculated without going thru all of the steps.
The right thing to do, is cancel this forecast and either follow method 2, or method 3 so that wings forecasters can be rewarded for their due diligence.
As of now, my flagging is only about not implementing correctly and letting you know, that you need to cancel this forecast and unfortunately will have to pay another deposit of 5000 Wings to relist.
I still stand by my statement that everyone should flag this project, as it has been implemeted wrong, and although I believe O.S.University wants to give 3% of their tokens to the community, how will they calculate rewards? Manually? And if so, are they going to manually send the reward to all the forecasters? This is the only way I see that it could be done.
Do what is right, cancel this forecast and either follow method 1 or method 2!
I have not came to the conclusion, that this project is a "scam" as of yet. However, I would like to see an explanation as to why some of the funds that have been contributed to your presale have been withdrawn from the crowdsale wallet to the address below and then used to invest into the RxEal crowdsale.
https://etherscan.io/address/0x24820b6cf0ef6c4c5a61e90970eddbf050ef7c3eLet me introduce myself - my name is Jordan Jambazov and I am the Technology Lead of the OS University project, as well as a co-founder of the project, actively involved with it since December 2016. The reason why I am stepping in the communication is because the way our WINGS project was set up is obviously wrong, and as you correctly suggested - there was a technological issue. What needs to happen is to cancel the forecast and proceed with Method #2 or #3.
During the last week we were actively trying to find a way to resolve the issue with the WINGS integration. Some of the options that we considered are: 1) migration of our existing presale contract to the WINGS smart contract and rewarding the investors through it - doesn't work, because WINGS smart contract lacks KYC support, which is essential for ICOs. 2) wrapping the WINGS EDU token smart contract with a new owner, which is another smart contract that could handle the KYC and we could still use the WINGS EDU token, without cancelling the project (doesn't work, as it violates the Keep It Simple principle & might contain security flaws). 3) cancel the forecast, and set up a new project with proper integration (Method #2 or #3)
In regards to your last question about the transaction of 1.2 ETH performed to address 0x24820b6cf0ef6c4c5a61e90970eddbf050ef7c3e - the transaction was made to our representative for Global Blockchain forum event in Santa Clara, which helped the OS University project to build traction within the international community there.