|
jwiz168
|
 |
August 11, 2016, 04:30:37 AM |
|
For those who want some Eggs, go Hunt and there are still some that are lurking (just like Pokemon Go).
|
|
|
|
|
|
wings.ai (OP)
|
|
August 11, 2016, 02:59:15 PM |
|
@wings.ai In the WINGS Specification Series #1 post it states: WINGS is going to leverage this consensus technology in order to create a last resort recovery for funds that are kept in the Rootstock side-chain. In the case the side-chain is breached, and funds are being transacted to a non-authorized address, a request will be submitted to the federation to cancel the transaction and restore the funds back. How is this different from the way Bitgo and Bitfinex were setup? Surely the federated members holding the keys in Rootstock are not going to manually go through every withdraw request for moving the transactions to the bitcoin main chain? They would likely have an automated system that approves legitimate transaction regardless if a person had come over these funds in a non-legitimate manner? If so, then this last line of resort doesn't really help Wings, this would be the equivalent as theDAO attacker making a withdraw request, and it would go through without any problems as the attacker had the control of the funds. I understand that it makes a good marketing point, but in reality, how much help is this last line of defence for stopping an attacker withdrawing funds from the Wings platform? Looking forward to the coming white paper specifications, they make for good reading! While this functionality is still under a design and discussion between us and RSK, the current approach is to withhold the transactions for a predefined amount of time, notifying the DAO owner and giving a chance to request it's cancellation (essentially rolling it back), then lock down the contract to prevent further funds draining. The vulnerability then could be resolved via contract upgrade, and distributed to other DAOs as well via the Wings platform mechanisms. |
|
|
|
110110101
Legendary
 Offline
Activity: 1382
Merit: 1002
|
|
August 12, 2016, 06:51:32 AM |
|
@wings.ai In the WINGS Specification Series #1 post it states: WINGS is going to leverage this consensus technology in order to create a last resort recovery for funds that are kept in the Rootstock side-chain. In the case the side-chain is breached, and funds are being transacted to a non-authorized address, a request will be submitted to the federation to cancel the transaction and restore the funds back. How is this different from the way Bitgo and Bitfinex were setup? Surely the federated members holding the keys in Rootstock are not going to manually go through every withdraw request for moving the transactions to the bitcoin main chain? They would likely have an automated system that approves legitimate transaction regardless if a person had come over these funds in a non-legitimate manner? If so, then this last line of resort doesn't really help Wings, this would be the equivalent as theDAO attacker making a withdraw request, and it would go through without any problems as the attacker had the control of the funds. I understand that it makes a good marketing point, but in reality, how much help is this last line of defence for stopping an attacker withdrawing funds from the Wings platform? Looking forward to the coming white paper specifications, they make for good reading! While this functionality is still under a design and discussion between us and RSK, the current approach is to withhold the transactions for a predefined amount of time, notifying the DAO owner and giving a chance to request it's cancellation (essentially rolling it back), then lock down the contract to prevent further funds draining. The vulnerability then could be resolved via contract upgrade, and distributed to other DAOs as well via the Wings platform mechanisms. Thank you wings.ai for the reply! I was thinking for this a bit more and was wondering who has the ultimate control of a DAO? Is it the DAO owner or will there be a meta-layer, so to say, that allows the wings platform to force said DAO contracts to wait in line before cashing out in terms of the DAO owner not being able to lock down the DAO? Say that there are 1 million DAOs working on the Wings network. In the case of a major hack like the slock.it-theDAO collapse, will it be required for each DAO creator to lock down their own DAOs and then cancel the contracts or can, or maybe should, the Wings platform assist in doing this for all DAOs? This would also mean that every DAO creator has the final saying for how the funds are used for every DAO contract? eg, the curator stands above the legality of the DAO contract? Would this be putting the DAO creator in a liable situation if the creator has the means of preventing theft but fails to do so? |
|
|
|
|
|
wings.ai (OP)
|
|
August 12, 2016, 12:46:22 PM |
|
@wings.ai In the WINGS Specification Series #1 post it states: WINGS is going to leverage this consensus technology in order to create a last resort recovery for funds that are kept in the Rootstock side-chain. In the case the side-chain is breached, and funds are being transacted to a non-authorized address, a request will be submitted to the federation to cancel the transaction and restore the funds back. How is this different from the way Bitgo and Bitfinex were setup? Surely the federated members holding the keys in Rootstock are not going to manually go through every withdraw request for moving the transactions to the bitcoin main chain? They would likely have an automated system that approves legitimate transaction regardless if a person had come over these funds in a non-legitimate manner? If so, then this last line of resort doesn't really help Wings, this would be the equivalent as theDAO attacker making a withdraw request, and it would go through without any problems as the attacker had the control of the funds. I understand that it makes a good marketing point, but in reality, how much help is this last line of defence for stopping an attacker withdrawing funds from the Wings platform? Looking forward to the coming white paper specifications, they make for good reading! While this functionality is still under a design and discussion between us and RSK, the current approach is to withhold the transactions for a predefined amount of time, notifying the DAO owner and giving a chance to request it's cancellation (essentially rolling it back), then lock down the contract to prevent further funds draining. The vulnerability then could be resolved via contract upgrade, and distributed to other DAOs as well via the Wings platform mechanisms. Thank you wings.ai for the reply! I was thinking for this a bit more and was wondering who has the ultimate control of a DAO? Is it the DAO owner or will there be a meta-layer, so to say, that allows the wings platform to force said DAO contracts to wait in line before cashing out in terms of the DAO owner not being able to lock down the DAO? Say that there are 1 million DAOs working on the Wings network. In the case of a major hack like the slock.it-theDAO collapse, will it be required for each DAO creator to lock down their own DAOs and then cancel the contracts or can, or maybe should, the Wings platform assist in doing this for all DAOs? This would also mean that every DAO creator has the final saying for how the funds are used for every DAO contract? eg, the curator stands above the legality of the DAO contract? Would this be putting the DAO creator in a liable situation if the creator has the means of preventing theft but fails to do so? There is no singular DAO creator by the way. Right now we are keeping our cards close to the chest as there is a lot of competition in the space, and will reveal the secret sauce strategically. Good question though  What sort of work do you do? |
|
|
|
110110101
Legendary
Offline
Activity: 1382
Merit: 1002
|
|
August 12, 2016, 01:26:51 PM |
|
@wings.ai In the WINGS Specification Series #1 post it states: WINGS is going to leverage this consensus technology in order to create a last resort recovery for funds that are kept in the Rootstock side-chain. In the case the side-chain is breached, and funds are being transacted to a non-authorized address, a request will be submitted to the federation to cancel the transaction and restore the funds back. How is this different from the way Bitgo and Bitfinex were setup? Surely the federated members holding the keys in Rootstock are not going to manually go through every withdraw request for moving the transactions to the bitcoin main chain? They would likely have an automated system that approves legitimate transaction regardless if a person had come over these funds in a non-legitimate manner? If so, then this last line of resort doesn't really help Wings, this would be the equivalent as theDAO attacker making a withdraw request, and it would go through without any problems as the attacker had the control of the funds. I understand that it makes a good marketing point, but in reality, how much help is this last line of defence for stopping an attacker withdrawing funds from the Wings platform? Looking forward to the coming white paper specifications, they make for good reading! While this functionality is still under a design and discussion between us and RSK, the current approach is to withhold the transactions for a predefined amount of time, notifying the DAO owner and giving a chance to request it's cancellation (essentially rolling it back), then lock down the contract to prevent further funds draining. The vulnerability then could be resolved via contract upgrade, and distributed to other DAOs as well via the Wings platform mechanisms. Thank you wings.ai for the reply! I was thinking for this a bit more and was wondering who has the ultimate control of a DAO? Is it the DAO owner or will there be a meta-layer, so to say, that allows the wings platform to force said DAO contracts to wait in line before cashing out in terms of the DAO owner not being able to lock down the DAO? Say that there are 1 million DAOs working on the Wings network. In the case of a major hack like the slock.it-theDAO collapse, will it be required for each DAO creator to lock down their own DAOs and then cancel the contracts or can, or maybe should, the Wings platform assist in doing this for all DAOs? This would also mean that every DAO creator has the final saying for how the funds are used for every DAO contract? eg, the curator stands above the legality of the DAO contract? Would this be putting the DAO creator in a liable situation if the creator has the means of preventing theft but fails to do so? There is no singular DAO creator by the way. Right now we are keeping our cards close to the chest as there is a lot of competition in the space, and will reveal the secret sauce strategically. Good question though What sort of work do you do? No problemo, fair enough I'll have to wait for the white paper or the upcoming blog posts. I'm a mechanical engineer so I have no background in computer science or the like... just your average crypto addict |
|
|
|
|
|
Sharky444
|
|
August 12, 2016, 03:03:55 PM |
|
Any ETA on when the ICO begins? Still this year?
|
|
|
|
davide72
Legendary
Offline
Activity: 2212
Merit: 1014
|
|
August 12, 2016, 03:07:25 PM |
|
I am glad to be part of this great project! |
|
|
|
|
|
Jian_Liux
|
|
August 12, 2016, 05:05:22 PM
Last edit: August 13, 2016, 01:29:34 AM by Jian_Liux |
|
Don't need to save BTC as of the moment . Eggs are available through different bounty schemes.
I know but I also noticed a lot of social media campaigns have closed already  twitter still gets Eggs you can also get FB like Eggs the newsletter referral was closed because of getting too much spam from Indonesia, China, Russia  I have claimed twitter and facebook bounty 1 month ago,but status still pending. It's true? |
|
|
|
|
syahril
Sr. Member
Offline
Activity: 434
Merit: 250
Bountie- Do You Have Game?
|
|
August 12, 2016, 05:49:15 PM |
|
Don't need to save BTC as of the moment . Eggs are available through different bounty schemes.
I know but I also noticed a lot of social media campaigns have closed already twitter still gets Eggs you can also get FB like Eggs the newsletter referral was closed because of getting too much spam from Indonesia, China, Russia I have claimed twitter and facebook bounty sejak 1 month ago,but status still pending. It's true? it's true brow ......!! I have claimed twitter and facebook bounty too but pending, regards indonesia mennnn !!!  |
|
|
|
|
jacaf01
|
|
August 12, 2016, 06:53:19 PM |
|
@wings.ai In the WINGS Specification Series #1 post it states: WINGS is going to leverage this consensus technology in order to create a last resort recovery for funds that are kept in the Rootstock side-chain. In the case the side-chain is breached, and funds are being transacted to a non-authorized address, a request will be submitted to the federation to cancel the transaction and restore the funds back. How is this different from the way Bitgo and Bitfinex were setup? Surely the federated members holding the keys in Rootstock are not going to manually go through every withdraw request for moving the transactions to the bitcoin main chain? They would likely have an automated system that approves legitimate transaction regardless if a person had come over these funds in a non-legitimate manner? If so, then this last line of resort doesn't really help Wings, this would be the equivalent as theDAO attacker making a withdraw request, and it would go through without any problems as the attacker had the control of the funds. I understand that it makes a good marketing point, but in reality, how much help is this last line of defence for stopping an attacker withdrawing funds from the Wings platform? Looking forward to the coming white paper specifications, they make for good reading! While this functionality is still under a design and discussion between us and RSK, the current approach is to withhold the transactions for a predefined amount of time, notifying the DAO owner and giving a chance to request it's cancellation (essentially rolling it back), then lock down the contract to prevent further funds draining. The vulnerability then could be resolved via contract upgrade, and distributed to other DAOs as well via the Wings platform mechanisms. Thank you wings.ai for the reply! I was thinking for this a bit more and was wondering who has the ultimate control of a DAO? Is it the DAO owner or will there be a meta-layer, so to say, that allows the wings platform to force said DAO contracts to wait in line before cashing out in terms of the DAO owner not being able to lock down the DAO? Say that there are 1 million DAOs working on the Wings network. In the case of a major hack like the slock.it-theDAO collapse, will it be required for each DAO creator to lock down their own DAOs and then cancel the contracts or can, or maybe should, the Wings platform assist in doing this for all DAOs? This would also mean that every DAO creator has the final saying for how the funds are used for every DAO contract? eg, the curator stands above the legality of the DAO contract? Would this be putting the DAO creator in a liable situation if the creator has the means of preventing theft but fails to do so? There is no singular DAO creator by the way. Right now we are keeping our cards close to the chest as there is a lot of competition in the space, and will reveal the secret sauce strategically. Good question though What sort of work do you do? No problemo, fair enough I'll have to wait for the white paper or the upcoming blog posts. I'm a mechanical engineer so I have no background in computer science or the like... just your average crypto addict Is this project not open source? I thought the codes need to be scrutinized by other coders. Just guessing not sure about this. |
|
|
|
110110101
Legendary
Offline
Activity: 1382
Merit: 1002
|
|
August 12, 2016, 07:47:27 PM |
|
...
Is this project not open source? I thought the codes need to be scrutinized by other coders. Just guessing not sure about this.
It hasn't been released yet, so there is nothing to see at the moment. I'm sure it will be released open source and all once it's ready. |
|
|
|
|
|
oneyesoneno
|
|
August 13, 2016, 01:34:50 AM |
|
...
Is this project not open source? I thought the codes need to be scrutinized by other coders. Just guessing not sure about this.
It hasn't been released yet, so there is nothing to see at the moment. I'm sure it will be released open source and all once it's ready. u can check their activity here https://github.com/ChainLab |
|
|
|
|
ltcrstrbrt
Legendary
Offline
Activity: 1568
Merit: 1057
|
|
August 13, 2016, 01:57:28 AM |
|
Btw, "wings.ai" I have two pull request on GitHub. Please take a look.
|
|
|
|
|
skypeTeo
Sr. Member
Offline
Activity: 365
Merit: 250
One Token to Move Anything Anywhere
|
|
August 14, 2016, 12:27:39 AM |
|
yet approved pending bonus?  |
|
|
|
|
wings.ai (OP)
|
|
August 14, 2016, 07:11:06 AM |
|
Btw, "wings.ai" I have two pull request on GitHub. Please take a look.
We going to handle all the pull requests with site translations soon. |
|
|
|
|
oneyesoneno
|
|
August 14, 2016, 11:15:31 AM |
|
yet approved pending bonus? u have to click those "claim" to get your rewards... try and see. |
|
|
|
|
|
jwiz168
|
|
August 14, 2016, 12:47:44 PM |
|
So, many have redeemed their July bounties. All that is left... whitepaper. Please dev release the third part of the series . There is really a high potential with this type of DAO. |
|
|
|
|
|
|
|
rorschach1
|
|
August 14, 2016, 11:54:26 PM |
|
Why is my newsletter subscription and twitter follow bonuses still pending?
|
|
|
|
|
|
jwiz168
|
|
August 15, 2016, 02:14:14 AM |
|
Why is my newsletter subscription and twitter follow bonuses still pending?
I think dev team is still waiting for the final number of tweets and clicks to subscribed newsletter. It will be done once the project has been launched. Hunt some more eggs and use twitter to spread the news but don't forget the #eggs in your tweet or else you will miss 2 eggs/tweet. |
|
|
|
|
|
