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
Implement Full Transaction Info #398
Comments
@tmedetbekov note the updated tasks list in description |
tmedetbekov
added a commit
that referenced
this issue
Jan 14, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 14, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 16, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 16, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 16, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 16, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 16, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 18, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 18, 2019
@tmedetbekov reopened the issue as the feature isn't fully implemented yet @TalgatNurdinov upload the slightly updated designs here:
|
https://app.zeplin.io/project/5b18ecff68e34a92986b0224/dashboard?seid=5b90faef4e79f19ceb4f2dbc
https://app.zeplin.io/project/5b18ecff68e34a92986b0224/dashboard?seid=5b90faef4e79f19ceb4f2dbc https://zpl.io/VxRPyYg |
tmedetbekov
added a commit
that referenced
this issue
Jan 21, 2019
tmedetbekov
added a commit
that referenced
this issue
Jan 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-- if I am sharing with someone transaction than I am basically sending a link to that transaction on selected block explorer.
-- test the feature with WhatsApp, Telegram and Facebook messenger.
-- On successful share the user should return back to transaction info. successful share should display "confirmation" checkmark/alert.
##Blockchain Explorers
BTC
-http://btc.horizontalsystems.xyz (default)
-https://btc.com (https://btc.com/api-doc#General (no access keys, supposedly no restrictions)
-https://blockexplorer.com/api-ref (no access keys, supposedly no restrictions)
-https://blockchair.com (no access keys, supposedly no restrictions)
-//IPFS(coming soon, do not add it now)
BCH
-http://bch.horizontalsystems.xyz (default)
-https://blockchair.com (no access keys, supposedly no restrictions)
-//IPFS(coming soon, do not add it now)
ETH
-http://eth.horizontalsystems.xyz (default)
-https://blockchair.com (no access keys, supposedly no restrictions)
-https://etherscan.io/apis (the free key on this API restricted to 5 calls/second. As an option we can ask the user to obtain his own free key(https://etherscan.io/myapikey) and use it. That would require an additional step on our end where user will be asked to add the API Key.
-//IPFS(coming soon, do not add it now)
The text was updated successfully, but these errors were encountered: