Let's pick a date for activating TAPI (WIP-00014) #1988
-
|
WIP-0014, aka TAPI introduces a mechanism for enabling risk-mitigated protocol upgrades by allowing block producers to signal support for specific protocol improvements, so that activation of those can automatically happen right after a supermajority of the network has signaled support for those rules for a certain period of time. WIP-0014 itself needs to be enacted by the traditional "will enter into force on this specific epoch" method. I'm working on an activation plan for WIP-0014. What would a suitable date for the activation be? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Does Tuesday, July 13th sound good to you? Under a hypothetical joint activation of WIP-0014 and WIP-0016, nodes would need to upgrade before July 27th to prevent any potential hard-forking risk. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a finalized (tagged) version for this already? Only tag I can find is tapi-rc1 which is rather old? |
Beta Was this translation helpful? Give feedback.
-
|
This is the PR porting TAPI into master: #1987 |
Beta Was this translation helpful? Give feedback.
-
|
And this is the PR with my activation proposal: witnet/WIPs#62 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but that does not indicate all the changes there will be to master once a final 1.3.0 version is created, making it impossible to judge the amount of necessary upgrade work. |
Beta Was this translation helpful? Give feedback.
Does Tuesday, July 13th sound good to you?
Under a hypothetical joint activation of WIP-0014 and WIP-0016, nodes would need to upgrade before July 27th to prevent any potential hard-forking risk.