1
00:00:14,230 --> 00:00:20,540
[HOST] Welcome to X1 Report, your source for the latest in blockchain news. Today, we're diving

2
00:00:20,540 --> 00:00:26,420
into the v4.0 upgrade plan for X1 Labs, as detailed by core developer Nick Pettas.

3
00:00:26,671 --> 00:00:31,923
[ANALYST] This update brings twelve feature gates, each designed to enhance the protocol layer of

4
00:00:31,923 --> 00:00:35,545
X1, bringing it closer in line with Solana's latest version.

5
00:00:35,795 --> 00:00:41,034
[HOST] First up, let's understand what a feature gate is. It's a dormant switch inside the

6
00:00:41,034 --> 00:00:46,652
validator client that activates consensus-affecting behavior only when a supermajority of

7
00:00:46,652 --> 00:00:49,239
stake runs a version that understands it.

8
00:00:49,489 --> 00:00:55,047
[ANALYST] X1 is not running experiments here; these gates are based on Solana Improvement Documents

9
00:00:55,047 --> 00:01:00,417
already tested in production. The sequencing is deliberate, with the p-token migration

10
00:01:00,417 --> 00:01:01,479
activating first.

11
00:01:01,729 --> 00:01:09,032
[HOST] The p-token migration, SIMD-0266, replaces the SPL Token program with a Pinocchio-based

12
00:01:09,032 --> 00:01:14,825
rewrite, reducing compute costs by 95-98% across the instruction set.

13
00:01:15,075 --> 00:01:20,124
[ANALYST] This change is significant because it frees up block space, allowing more transactions to

14
00:01:20,124 --> 00:01:25,230
be processed. However, off-chain indexing will need updates due to three new instructions.

15
00:01:25,480 --> 00:01:32,512
[HOST] Next, we have stake program v5, SIMD-0490, which upgrades the core-BPF Stake program to

16
00:01:32,512 --> 00:01:39,464
version 5.0.0. It introduces a minimum delegation of 1 XNT, impacting the long tail of

17
00:01:39,464 --> 00:01:40,596
dust accounts.

18
00:01:40,846 --> 00:01:47,142
[ANALYST] On Solana, this rule would have priced out many small delegators, but on X1, it's much

19
00:01:47,142 --> 00:01:49,998
more affordable at about $0.39 per XNT.

20
00:01:50,248 --> 00:01:56,515
[HOST] Another important change is the delayed commission, SIMD-0249. It ensures that commission

21
00:01:56,515 --> 00:02:02,642
changes take effect a full epoch later, preventing validators from capturing unexpected

22
00:02:02,642 --> 00:02:03,135
yields.

23
00:02:03,385 --> 00:02:08,439
[ANALYST] This change protects delegators by aligning the commission field with the epoch snapshot,

24
00:02:08,439 --> 00:02:10,937
reducing the risk of last-minute rate hikes.

25
00:02:11,187 --> 00:02:19,778
[HOST] Moving on to cryptography, we have three gates: SIMD-0284 for little-endian input and

26
00:02:19,778 --> 00:02:28,672
output, SIMD-0302 for BN254 G2 group operations, and SIMD-0388 for BLS12-381 operations.

27
00:02:28,922 --> 00:02:34,108
[ANALYST] These upgrades lay the groundwork for advanced cryptographic protocols and proof systems,

28
00:02:34,108 --> 00:02:36,964
making X1 more versatile for future developments.

29
00:02:37,214 --> 00:02:43,701
[HOST] The safety block includes SIMD-0340, which validates chained block IDs, and SIMD-0459,

30
00:02:43,701 --> 00:02:50,264
which restricts syscall parameter addresses. Together, they enhance the security of the

31
00:02:50,264 --> 00:02:50,868
network.

32
00:02:51,118 --> 00:02:58,257
[ANALYST] Finally, enable_sbpf_v3_deployment_and_execution bundles three SIMDs to allow X1 to deploy

33
00:02:58,257 --> 00:03:03,811
and execute SBPFv3 programs, expanding its computational capabilities.

34
00:03:04,061 --> 00:03:09,747
[HOST] With all twelve gates activated, X1 will see significant improvements in block space,

35
00:03:09,747 --> 00:03:15,233
security, and computational flexibility. Validators should prepare for the release

36
00:03:15,233 --> 00:03:19,247
announcement and the buffer deployment required for gate #7.

37
00:03:19,497 --> 00:03:24,347
[ANALYST] No activation epochs have been published yet, but we'll track them as they are announced.

38
00:03:24,347 --> 00:03:26,963
The running log is available on Community Pulse.