Topics
We discussed the purpose of product integrity, the ability for us to detect ways for things to go wrong, and to come up with solutions before they do.
-
What’s in scope
- Legal and Blockchain Dev
- Thread DApps
- The FrabricDAO DApp
- Legal corporate entities holding the property
- Link between corporate entities and Threads
- Link between corporate entities and the FrabricDAO
What was discussed
-
@colin mentioned an 2x2 matrix between both the legal and dev contracts, as we have both a legal and development obligation at multiple levels
-
The conversation moved to Upgrade proposals for both Threads and the FrabricDAO itself
- upgrading the main DAO and how that will propegate through threads
- upgrading threads
- blackhats could get a proposal through that looks like a FrabricDAO upgrade request but isn’t
- two paths:
- Only upgrade path via the FrabricDAO
- proposals for upgrades are only eligible from the FrabricDAO contract
- If tokenholders of a thread want to add their own features and go their own way, they would have to vote to leave the frabric network (ragequit)
- challenge: this wouldn’t provide mechanisms for tokenholders to be able to truly control and manage their own project
- Enable upgrades from tokenholders and FrabricDAO members
- Tokenholders could make proposals to upgrade their Thread, alongside FrabricDAO
- Would give flexibility for tokenholders to determine what feature sets they want, forking the standard thread contracts to adjust to their specific usecases
- challenge: could lead to situations where malicious devs are able to push code into threads unchallenged without rigorous testing; causing a “rugging” of the thread
- Possible improvement: require tokenholders who want to ship upgrade proposals to be approved by the frabricDAO as an independent dev, which can be revoked and permanently banned if they mess up
- other thoughts
- no semantic versioning
- changelog is a source of truth, if the changelog is wrong; proposal should fail
- another potential thing to explore; make thread source code adjustments separate from upgrade proposals
- feature flags for selecting different upgrade paths?
- example path
- thread proposes an upgrade
- thread makes a change
- dao proposes an upgrade
- thread takes the upgrade, and previous code is not guaranteed to be there
- there should be a warning that an upgrade proposal can edit the existing contract
- investors will need to be notified (UI, EPNS) that the investment that they’re making into a property that may have forked off of the FrabricDAO source standard
- threadcode fractional v1, threadcode unknown? as definitive ideas
-
Should thread information be publicly available or private?
- thread can own threads (or a different primitive will enable this)
- there may be competitors who are interested in these same properties
- there could be dataminers
- Why would other people share information about the purchase
- This should really only work for funds / consortium
- if there is any private financial information that you’d like to discuss, you should take it to a different location
-
how do you deal with the legal linkage between the DAO and the deed?
- Technically the property tokens don’t have direct ownership of the property
- The corporate entity generally listens to the tokenholders
- bond slashing mechanism prevents rugpulling to actually gain cash
- each governor is a shareholder for multiple properties
- would have to make a mechanism to increase collateral if the home price has increased by X%
- example
- if we see a house price go up by 20%
- we ask them to increase collateral by 20%
- the governor is now undercollateralized
- Voting
- minimum of 3 governors per thread
- how do we scale voting in/out of governors and threads
- already discussing a script to automate services, validate proposals - etc
- anyone can submit a proof; ignore this proposal
- get the value cap of a thread, calculate the bonding limit for a governor
- how to avoid GP/LP liability of tokenholders
- documentation is something we’ll need to explicitly define this
- some jurisdictions have unlimited liability for DAOs and DAO treasury
- making sure it’s written down and explained as to why you will not have unlimited liability