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

404 for link in README #46

Closed
ligi opened this issue Apr 2, 2019 · 7 comments
Closed

404 for link in README #46

ligi opened this issue Apr 2, 2019 · 7 comments

Comments

@ligi
Copy link

ligi commented Apr 2, 2019

was very excited to read: "Java-Implementation of a native-wrapper" but then clicked on in and got a 404 :-(

@simon-jentzsch
Copy link
Contributor

Yes we have put in the examples already, but the link will work as soon as we will publish the our c-implementation repo. But a 404 is not nice ;-) so I'll remove the link and add a comment.

@ligi
Copy link
Author

ligi commented Apr 16, 2019

thanks! Hope the repo opens soon. If you need beta-testers let me know - really eager to add in3 support to WallETH ;-)

@simon-jentzsch
Copy link
Contributor

yes, I hope so as well. Our current plan would be to release it in Q2 this year, which is very likely to happen. If you want, we can have a chat to see, if you can test even the current version earlier.

@ligi
Copy link
Author

ligi commented May 16, 2019

happy to chat - are you on [matrix]

@ligi
Copy link
Author

ligi commented Jul 8, 2019

@simon-jentzsch any news on the release? Eagerly awaiting it and it seems it will not be Q2 anymore if you are not in possession of a time machine ,-)

@dominicletz
Copy link

Yep, also looking for the c-client. What's the ETA?

simon-jentzsch added a commit that referenced this issue Jul 22, 2019
Resolve "toMinHex() bug"

Closes #46 and #50

See merge request in3/ts/in3!46
simon-jentzsch added a commit that referenced this issue Aug 5, 2019
Resolve "Increase transport timeout"

Closes #46

See merge request in3/ts/in3!44
@dominicletz
Copy link

@simon-jentzsch was this intentionally closed? The links in the readme still lead to a 404 -- at least for me...
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants