Skip to content
This repository has been archived by the owner on May 13, 2022. It is now read-only.

[Client] passing string for byte32 is not consistent for eris-contracts and e-pm #189

Closed
benjaminbollen opened this issue Aug 2, 2016 · 2 comments
Closed

[Client] passing string for byte32 is not consistent for eris-contracts and e-pm #189

benjaminbollen opened this issue Aug 2, 2016 · 2 comments
Labels
triaged/response needed triaged/will fix
Milestone
0.16.0

Comments

@benjaminbollen
Copy link
Contributor

No description provided.

@compleatang compleatang changed the title passing string for byte32 is not consistent for eris-contracts and e-pm [Client] passing string for byte32 is not consistent for eris-contracts and e-pm Oct 13, 2016
@compleatang compleatang added this to the 0.16.0 milestone Oct 13, 2016
@compleatang
Copy link
Contributor

Ben, is this done?

@silasdavis
Copy link
Contributor

@benjaminbollen can you elaborate, also does this relate to: #149 or #188 ?

@silasdavis silasdavis mentioned this issue Apr 26, 2017
Closed
@smblucker smblucker mentioned this issue Jan 25, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
triaged/response needed triaged/will fix
Milestone
0.16.0
Development

No branches or pull requests
3 participants
@silasdavis @compleatang @benjaminbollen