-
Notifications
You must be signed in to change notification settings - Fork 217
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
Transaction integration tests #301
Conversation
("POST", "v2/wallets/" <> widSrc <> "/transactions") | ||
Default payload | ||
verify r | ||
[ expectResponseCode HTTP.status202 |
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.
I don't know why this request is giving me 403
. Everything works fine with curl
....
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.
you can't do multi-output transactions at the moment with those faucet wallets. That's something I wanted to enable yesterday but time flies. Since there's only a single UTxO on the faucet wallet at the moment, you can only have a single output recipient :)
We need to send more than one output on the faucet wallet and have let's say, one million ADA, but not as 1x1M, but 10x100_000 !
--post transaction | ||
r <- request @ApiTransaction ctx ("POST", postTx wa) Default payload | ||
verify r | ||
[ expectResponseCode HTTP.status202 |
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.
Same here... 403
¯_(ツ)_/¯
f4ada18
to
1076b8c
Compare
1076b8c
to
b39bc4a
Compare
b39bc4a
to
7a54384
Compare
7a54384
to
805def1
Compare
805def1
to
2cbf1b4
Compare
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.
👌
2cbf1b4
to
2f8ced6
Compare
…was not true .... 🤦
Fees are actually not necessarily fixed. They depend on the ix of the input picked. Since we generate all fixture wallets with an initial transaction with 1K outputs, ix can go from 0 to 999, and therefore be encoded on 1, 2 or 3 bytes. This depends on which input are assigned to which wallet. As a consequence, it is easier (and more correct) to look at a range of fees, in case inputs ix gets encoded on 1 or 3 bytes
2f8ced6
to
6b0e560
Compare
Issue Number
Overview
Comments