Renato (@RenatoPulse) header
Renato (@RenatoPulse) profile picture

Pulsechain Genesis Holder

Italia
Joined May 2010
Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)Photo by Renato (@RenatoPulse)
The cutoff allows historical block bodies and receipts before block 26M to be pruned, reducing storage requirements while preserving the data needed for chain validation. Go-Pulse must then be recompiled. The actual removal of historical data requires a separate pruning operation
1
1
52
I don't know how long it will remain reliable, as this isn't an official release but a recent customization of my own. It needs more testing across different clients and over a longer period. However, synchronization is currently working fine for running a validator-only node.
1
36
I'm validating on #PulseChain with history pruning: modified Go-Pulse 3.3.0-pulse-stable + Lighthouse-Pulse 2.5.1. ~382 GB vs a ~1.2 TB baseline (~68% less). Lower storage costs could make nodes more accessible and strengthen decentralization. @bretep, thoughts? @RichardHeartWin
3
4
1
16
534
I modified two files in Go-Pulse: core/blockchain.go — Added a fixed cutoff at block 26M and freezer tail validation. core/rawdb/freezer_table.go — Added proper handling for databases without freezer support.
1
1
2
96
3+ years. 3 forks behind. 0 scheduled. #Ethereum shipped Cancun, Prague, Osaka. Soon #Glamsterdam. #PulseChain after Shanghai only nil, nil.. diff +4 lines. that's the whole PR. someone just needs to type it. is keeping up necessary for adoption? @bretep @RichardHeartWin #Hex
5
245
Unpopular opinion: respect to all devs, but instead of saying we’ll do better than existing services, we should aim for integration and support from them. We need adoption. @RichardHeartWin #pulsechain #pls #plsx #inc #hex @bretep #provex
1
3
142
#PulseChain vs #Eth: current EIPs implementations. @bretep @RichardHeartWin There're skilled people in the community ready to help and support devlp. It would be great to create a constructive discussion channel,unlike the current tg groups, where you get banned for simply ask.
6
5
26
1,385
🚨 BREAKING: Binance is listing PulseChain… even @cz_binance finally got it ! @RichardHeartWin #PulseChain $PLS $PLSX $HEX #Hexican
2
2
5
241
Do you have any NFTs stuck on the #Mintra marketplace? I built this UI to help you recover them renatopulse.netsons.org/Mint… #pulsechain #pls #plsx #inc #hex
4
4
1
9
273
Massive result! Proof of how powerful teamwork in this community is! 🔥🍾 Now straight ahead to flip ETH! #Pulsechain $pls $plsx #hex #hexican @RichardHeartWin @bretep #sourcify
#PulseChain is now the chain with the 2nd highest number of verified contracts on @SourcifyEth - whereas not long ago we weren't top 10 - all thanks to @RenatoPulse and myself. We aim to improve security, transparency and user experience on the block explorers. @RichardHeartWin
1
1
4
303
#PLSX Staking Contract (PLSXLab) Did you know the #Pulsechain deployer address (0x30e..2539) has also released the PLSX staking contract? I verified it for you on #Sourcify: repo.sourcify.dev/369/0x3E3E… @bretep when UI? When staking ? 😁 #PLS #RH #Hex #INC #Hexican #RichardHeart
3
11
416
Hey @ProveXCom @bretep , I’ve verified the contracts on Sourcify for the community, so all explorers and tools (including Otter) can now correctly load and display transaction information. #ProveX #Pulsechain #PLS #PLSX #HEX #INC
1
1
7
244
3/4 | 0x94F510fa245843Ff5eDa2d18479FE63ac51F8fE6 - PostIntentHookRegistry 0x689F82b4078aA07F443af9ae308534bD2Ff545D3 - RelayerRegistry 0x4AeA2288ec542963256b66D70EfddF4cB8754f82 - NullifierRegistry 0x7238d0B6a28a3a6e3DfCd281D7Cb9b3250B30EA6 - EscrowRegistry
1
1
109
4/4 | 0x31dD72E1a385F98F4e6A94330c8121d2Ed62Ab72 - ProtocolViewer 0x49DAd1f29a3FE2E4D90a59e6687d9f7A2836B4a8 - SimpleAttestationVerifier
1
84
Over the past few weeks, I have verified more than 200k contracts on #Sourcify. #PulseChain has now officially surpassed BNB Chain in the total number of verified contracts. docs.sourcify.dev/docs/chain… Tell RH, blocking people who actually contribute #PLS @Bretep #PLSX #INC #HEX
1
3
147
Hey @GigaTheMinter, I’m working on improving the transaction details for your scan. I’m verifying all PulseX PLP token contracts on #Sourcify, it’s a long run, but I’ll get through them. @SourcifyEth thanks for the “Similarity” API v2, this approach is much faster. #Pulsechain
3
7
770
I built a tool that clones #Sourcify verification from an #ETH fork contract to #PulseChain, allowing automatic retrieval by OtterScan and Sourcify-based Blockscout explorers. renatopulse.netsons.org/sour… @SourcifyEth could you implement this natively? 😄 @bretep $PLS $PLSX
2
6
177
I've personally verified the following smart contracts on #Sourcify, previously, they were not verified, and they are now aligned with Otter #PulseChain #cUSDC #cDai #cBAT #cREP #cSUSHI #cWBTC #USDC
1
3
203
@SourcifyEth #PulseChain is derived from an Ethereum fork, meaning that smart contracts are reproduced identically. As a result, contract validation can be automated without re-downloading and re-validating the same contracts, with the only difference being the Chain ID (369) ?
78