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
Copy file name to clipboardExpand all lines: docs/develop/guides/injective-101/whitelist.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Contract upload on Injective requires governance approval. This structure has be
15
15
16
16
This governance process is time-consuming for validators and the community. Injective builders additionally face a 4-day wait to roll out features, affecting developer experience and user growth.
17
17
18
-
As of the [Altaris chain upgrade](../../../nodes/Validators/mainnet/canonical-chain-upgrade/canonical-1.13.0.md), it is now possible to request whitelisting your address for contract uploads.
18
+
As of the [Altaris chain upgrade](../../../nodes/validators/mainnet/canonical_chain_upgrade/canonical-1.13.2.md), it is now possible to request whitelisting your address for contract uploads.
19
19
20
20
# Submission Guidelines
21
21
@@ -31,7 +31,9 @@ In order to be considered for a whitelist approval, it is strongly recommended t
31
31
Users that meet these criteria will have a greater chance at receiving whitelist permissions:
32
32
33
33
1. The project has completed Injective Foundation KYC/KYB and the team members' identities are known to the community.
34
+
34
35
- Exception: Anonymous developers with proven credibility and successful apps in other ecosystems.
36
+
35
37
2. The project has been live on mainnet for at least 1 month and has achieved significant TVL/usage.
0 commit comments