You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's a serious business blocker for us as we're implementing accounts as per new ERC-4337. Signer becomes a separate entity and it's not the same as NFT owner / order maker.
All but sell SDK operations (mintAndTransfer, directPurchase, safeTransfer, burn, cancel) are happening in the background via direct eth_sendTransaction calls. The sell happens differently: eth_signTypedData_v4 and then api/orders. We were able to upgrade all eth_sendTransaction logic without any changes on your end but the flow of sell logic makes it harder / impossible for us.
Eventully as a plan b - do we have any way to list NFT for sale without using your API / indexer?
The text was updated successfully, but these errors were encountered:
I have a question / issue regarding your order validator service:
https://github.com/rarible/ethereum-indexer-public/blob/8061d075baf19ea6bb59fe56820fa8a96cd21a65/order/api/src/main/kotlin/com/rarible/protocol/order/api/service/order/validation/validators/OrderSignatureValidator.kt#L49
Your logic for validating signature is based on ERC-1271. Any chance you could upgrade it to ERC-6492?
Example implementation
https://github.com/AmbireTech/signature-validator
That's a serious business blocker for us as we're implementing accounts as per new ERC-4337. Signer becomes a separate entity and it's not the same as NFT owner / order maker.
All but sell SDK operations (mintAndTransfer, directPurchase, safeTransfer, burn, cancel) are happening in the background via direct eth_sendTransaction calls. The sell happens differently: eth_signTypedData_v4 and then api/orders. We were able to upgrade all eth_sendTransaction logic without any changes on your end but the flow of sell logic makes it harder / impossible for us.
Eventully as a plan b - do we have any way to list NFT for sale without using your API / indexer?
The text was updated successfully, but these errors were encountered: