-
Notifications
You must be signed in to change notification settings - Fork 0
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
add sending value along tx data #23
base: main
Are you sure you want to change the base?
Conversation
How was this request encoded? It looks like the format is incorrect. $ cast abi-decode "acceptRequestBatch(uint256[] calldata,uint256[] calldata,address[] calldata,uint256[] calldata,address[] calldata)" 0xa93c531700000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000016000000000000000000000000000000000000000000000000000000000000001a00000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000100000000000000000000000038f0fa12ff9d87345186995d2bece9612309ba4a0000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Error: no data was decoded |
Considering this value I was able to decode it using our Response:
|
|
Found the issue!
The |
@ScreamingHawk how much work would it be to add support for I spoke with Lukas and it sounds like we're using We're unsure how to resolve this issue - how to buy multiple items in the cart with native currency. If we split each item to its own transaction, it'd likely lead to a bad UX, since user would needs to sign multiple buy transactions individually. What's the recommended next steps? |
Good news. The marketplace is upgradeable so we should be able to perform an upgrade with the added functionality without changing the contract address. This would require some testing and would be a couple days of work to get it deployed on all chains. |
0xsequence/marketplace-contracts#7 Marketplace update for reference |
0xsequence/marketplace-contracts#8 Will be deployed at {
type: 'function',
name: 'acceptRequestBatch',
inputs: [
{ name: 'market', type: 'address', internalType: 'contract ISequenceMarketFunctions' },
{ name: 'requestIds', type: 'uint256[]', internalType: 'uint256[]' },
{ name: 'quantities', type: 'uint256[]', internalType: 'uint256[]' },
{ name: 'recipients', type: 'address[]', internalType: 'address[]' },
{ name: 'additionalFees', type: 'uint256[]', internalType: 'uint256[]' },
{ name: 'additionalFeeRecipients', type: 'address[]', internalType: 'address[]' }
],
outputs: [],
stateMutability: 'payable'
} Note this doesn't work with requests that use ERC20s. This should only be used for native token requests. |
@ScreamingHawk Cool, thanks for the update! 🎉
Is there anything we can do to support both ERC20 and native tokens in a single transaction for both types? If not, I wonder what our Marketplace is supposed to do -- do we need to group native vs. ERC-20 collectibles into two different cart transactions? |
@ScreamingHawk Thank you for the update, that's great. @LukasJenicek Do you mind finalizing this PR and resolving conflicts when you get a chance? I would like to merge this in, it's a handy addition. |
CLI send transaction
Giving me
Get Orders on Indexer:
Response