Comments (3)
Agreed.
Here's my understanding so far: We want our process to be as thorough as necessary while also as light and nimble as possible. Before we commit to changes, we want to ensure the code, design, and security analysis all match, so we need to get the engineering and science teams synchronized on these kinds of changes.
However, for nimbleness and speed, we don't want a process that's too heavy. For that reason, I suggest that for now we:
- can make design changes first, then do both engineering implementation and science review independently from there. This means we may do engineering work on something only to learn later than some scientific flaw is discovered, but I think that risk is worth it in order to have faster engineering progress.
- do review / analysis process with a combination of github PRs to the specs / design docs (in this repo) as well as meeting topics, ml posts, etc...
- don't use bip/pip-style proposal / acceptance review until "1.0 feature freeze" timeframe.
from zips.
I have a draft ZIP 0 describing the process, which is based very loosely on BIP 1.
from zips.
We're now revisiting this goal and talking about the ZIP process.
from zips.
Related Issues (20)
- [ZIP 320] Transparent-source Addresses
- [protocol spec] Spec uses inconsistent terms for ask and ak
- Finalize design of v6 transactions
- Keep a public table of wallet capabilities HOT 1
- ZIP 317: Proportional Transfer Fee Mechanism HOT 1
- Revise ZIP-316 to concede mixed indexes in UAs HOT 6
- ZIP-316 should clearly call out that wallets may need to scan multiple T addresses
- Draft a ZIP to provide best practices for Wallet App EOS/EOL
- ZIP clarifications
- ZIP process: ZIP 0 is unclear on the requirements to make a substantive update to a deployed ZIP
- [ZIP 228] Asset Swaps for Zcash Shielded Assets
- Document that the Bech32 Sapling viewing keys aren't diversifiable and that you might want to use a UVK instead
- Generate transactions to self if needed in order to respect the transparent address gap limit
- [ZIP-315] Condense all specified requirements into a table to track wallet compliance.
- [ZIP-315] TODO's documented on DRAFT
- ZIP 316: clarify that lengths and typecodes are constrained to be <= MAX_SIZE (0x2000000)
- based zcash address decentralized IP address, Abolish ipv4 and ipv6
- ZIP 0: Update "ZIP Status Field" section to permit multiple statuses for living ZIPs
- ZIP-316 revision 1 effectively blocks 1 transparent receiver HOT 9
- ZIP 320: Update for decision to use TEX addresses
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from zips.