Be a crypto hero in the market by logging in
Don't you have an account? Sign in
Market trends report
Today we released the beta3 update to EOSJS v20.0.0. There are breaking changes in the release, so it is important for integrators to have their dependency versions locked. The changes in the release are a further step towards our plan to enable Dapp developers to integrate with one universal api and automatically support any key management and signing solution of their users’ choice.
Feedback is welcome on our continued advancement of developer tools and resources for the EOSIO Developer Community. Feel free to get in contact with our Developer Relations team by emailing email@example.com with your thoughts on how we can improve software development for the community.
Continue reading below to learn more about EOSJS v20.0.0-beta3.
Remove dependency on eosjs-ecc (#425)
In this release, we removed the “default” signature provider from the default export. Keeping this out of the default export prevents eosjs-ecc from being bundled automatically, significantly reducing bundle size. We made this change to heighten user security across applications by encouraging the use of signature providers instead of having users paste private keys directly into applications. In the future, we hope that most eosjs implementations will leverage an alternate signature provider to enhance user security.
Support for React Native Apps (#425)
We’ve made necessary updates to ensure eosjs is compatible with React Native Apps and the Edge/IE11 browser.
Support for Signature Providers to Modify Transactions (#418)
As we move to a more secure method of key handling within applications built on EOSIO, signature providers may have valid reasons to modify a transaction (i.e., add actions) prior to returning it to the API transact method for possible broadcast. Prior to this update this was not possible, as signature providers could only return signatures, and transact uses the same serialized transaction that was passed into the signature provider. With this update, the signature provider now returns an object with two keys: signatures and serializedTransaction. The transact function then broadcasts this output.
Improved Handling of Multisig Transactions (#432)
Finally, we have made some updates to provide better support for multisig transactions on EOSIO.
More details for this release can be found on GitHub in the Release. Remember, EOSJS V20 is still in beta and will be updated frequently to enhance the security and usability of the library. Remember to lock your dependencies.
As always, if you are interested in providing feedback and working more closely with our team to improve EOSIO for the community, you can send our developer relations team an email at firstname.lastname@example.org. You can also hear about future updates by subscribing to our mailing list on the EOSIO Developer Portal. We are excited to be continually improving the usability of the software for EOSIO developers as we continue laying a foundation for the mass adoption of blockchain technology.
EOSJS Version 20-beta3: React Native Support and Enhancements for Signature Providers was originally published in eosio on Medium, where people are continuing the conversation by highlighting and responding to this story.
위켄 눈여겨보고있는데 좋은소식이네요 ^^
Community | B캐피탈리스트 투자 유치 세션 진행
Community | B캐피탈리스트 투자 유치 세션 진행
Community | 토큰뱅크실체
안녕하세요 고객님. 신청해주신 순서대로 차례대로 OTP 초기화를 진행해드리고 있습니다. OTP 초기화가 진행된 후에 이메일 답장이 갈 예정이니 이메일 확인하신 후 재등록 진행해주시면 감사하겠습니다.
Community | OTP 초기화 신청했는데요
안녕하세요 고객님. 혹시 모바일에서 휴대폰 인증을 진행하신건가요? 토큰뱅크 휴대폰 인증의 경우에는 PC를 이용하여 진행해주셔야 합니다.
Community | 휴대폰 인증이 화면이 바뀌고 오류주소로 뜹니다
Write a post
Are you sure you want to delete this post?
Are you sure you want to delete this comment?
Purchase has been completed.
닉네임을 설정 후 작성해주세요.