-
Notifications
You must be signed in to change notification settings - Fork 2
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
Send assets flow #20
Send assets flow #20
Conversation
dgca
commented
Oct 31, 2023
@@ -0,0 +1,114 @@ | |||
import { BoxKeyPair } from "@ironfish/rust-nodejs"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just renamed this file from /ironfish/index.ts
to /ironfish/Ironfish.ts
to keep the pattern of index files being route handlers.
@@ -0,0 +1,56 @@ | |||
import { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only real change in the /main/api/
folder is this new file that handles sending a transaction to the Iron Fish node.
toAccount: data.toAccount, | ||
assetId: data.assetId, | ||
amount: parseIron(data.amount), | ||
fee: parseInt(fee, 10), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ore values should be treated as bigints rather than numbers (since they're i64 values). It's unlikely to be an issue with fees anytime soon, since supply of the native currency is lower, and fees in general are low, but might be worth standardizing all operations on ORE/IRON everywhere to avoid any accidental parsing bugs, like the parseIron
function you have above