Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address Eli's review comments about transactions #32

Closed
daira opened this issue Mar 30, 2016 · 2 comments
Closed

Address Eli's review comments about transactions #32

daira opened this issue Mar 30, 2016 · 2 comments

Comments

@daira
Copy link
Collaborator

daira commented Mar 30, 2016

We confusingly attribute agency to transactions.

@daira daira self-assigned this Mar 30, 2016
@defuse
Copy link
Contributor

defuse commented Apr 12, 2016

Philosophizing: It definitely goes against the grain, but it's consistent to think about protocol messages as being agents, and the protocol "participants" being just some state. The messages are little programs (hopefully not Turing-complete) that make changes to the participants' state. That's more intuitive to me, but let's go with whatever's more standard and easier for cryptographers to review.

@daira
Copy link
Collaborator Author

daira commented Sep 4, 2016

Fixed in 2016.0-beta-1.

@daira daira closed this as completed Sep 4, 2016
daira pushed a commit to daira/zips that referenced this issue Nov 8, 2023
)

This adds to the specification to provide wallets instructions on displaying Asset information to users in an unambiguous way.

This addresses [this comment](zcash#680 (comment)).
daira pushed a commit to daira/zips that referenced this issue Feb 7, 2024
)

This adds to the specification to provide wallets instructions on displaying Asset information to users in an unambiguous way.

This addresses [this comment](zcash#680 (comment)).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants