We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We created two PoCs to help determine the best option for including the track fields
Onchain trackid via paymentReceiver & refundReceiver Onchain Identifier via transaction data and calldata
The final decision is to include the trackId in the data field. This issue aims to resolve that and create the final implementation.
trackId
OnChain tracking PoC issue
The text was updated successfully, but these errors were encountered:
data
calldata
DaniSomoza
Successfully merging a pull request may close this issue.
Context / issue
We created two PoCs to help determine the best option for including the track fields
Onchain trackid via paymentReceiver & refundReceiver
Onchain Identifier via transaction data and calldata
Proposed solution
The final decision is to include the
trackId
in the data field. This issue aims to resolve that and create the final implementation.Links
OnChain tracking PoC issue
The text was updated successfully, but these errors were encountered: