From e773cd2d501b63ed91af240e649b5afc0b532d4c Mon Sep 17 00:00:00 2001 From: Daniel Somoza Date: Mon, 20 Jan 2025 17:45:35 +0100 Subject: [PATCH 1/2] add onchain tracking version label and form link --- pages/sdk/onchain-tracking.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/pages/sdk/onchain-tracking.mdx b/pages/sdk/onchain-tracking.mdx index c294031e..9677d8a0 100644 --- a/pages/sdk/onchain-tracking.mdx +++ b/pages/sdk/onchain-tracking.mdx @@ -1,4 +1,4 @@ -import { Tabs, Steps } from 'nextra/components' +import { Tabs, Steps, Callout } from 'nextra/components' # On-chain Tracking @@ -8,6 +8,10 @@ Implementing a Safe on-chain identifier enables tracking of complex data, such a By submitting your on-chain identifier through the form provided at the end of this page, you will help us accurately attribute activity and allow us to return value to our Ecosystem Partners in the future. + + On-chain tracking supported in [Protocol Kit](../sdk/protocol-kit.mdx) `v5.2.0` and [Relay Kit](../sdk/relay-kit.mdx) `v3.4.0` or later. + + ## On-chain identifier format The identifiers used to track Safe deployments and transactions are 50 bytes in length and follow the format below: @@ -215,6 +219,8 @@ The on-chain identifier allows tracking the deployment of Safe accounts, the exe ## Submission Form +You can fill out the form by clicking [this link](https://forms.gle/NYkorYebc6Fz1fMW6) or using the form below: +