PulseChain Dev Activity
418 subscribers
2.99K links
Download Telegram
PulseChain activity

Bret pushed new project tag v2.1.0 at PulseChain / hex-server

Bret (a5921b5f) (https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.0) at 17 Jul 00:14

Update release version v2.1.0

2026-07-17 00:14:28 +00:00

https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.0
PulseChain activity

Bret pushed new project tag v2.1.1 at PulseChain / hex-server

Bret (fbfb1829) (https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.1) at 17 Jul 02:33

Update release version v2.1.1

2026-07-17 02:33:28 +00:00

https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.1
👎1
PulseChain activity

Bret pushed new project tag v2.1.2 at PulseChain / hex-server

Bret (54144c01) (https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.2) at 21 Jul 01:23

Update release version v2.1.2

2026-07-21 01:23:53 +00:00

https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.2
👎1
PulseChain activity

Crypto StarterAcademy commented on issue #267 at PulseChain / PulseChain Mainnet

Thanks, Bret. That confirms that the endpoint is available for public use.

To keep our monitoring conservative and avoid placing unnecessary load on the service, could you please confirm whether there are any published or recommended:
rate or concurrency limits;
timeout, batch or response-size limits;
restrictions on the methods listed above;
history or pruning limits, including historical state for eth_call?


Could you also confirm whether rpc.pulsechain.com is operated directly by the PulseChain team or uses a third-party upstream?

A link to existing documentation or a brief high-level confirmation would be sufficient.

2026-08-01 21:11:44 +00:00

https://gitlab.com/pulsechaincom/pulsechain-mainnet/-/issues/267#note_3632912637
PulseChain activity

Bret commented on issue #37 at PulseChain / PulseChain Mainnet

Restored by the moderation bot: this comment was removed in error during an automated review of the project's history, and is reinstated here with its original author credited.

Originally posted by @cfreeman4 (https://gitlab.com/cfreeman4):

IT WORKED!!!!! So I've been reading about spiking the gas prices beyond normal limits and I gave it a try. Before the transaction goes though, change the Max fee, Priority fee and Gas fee to in insanely high number regardless of the wanring message. It did the trick. It pushed it all through. I did 8000000 Max fee, 2000000 Priority fee, and 500000 Gas fee in Advanced settings of the transaction. It will either show Advanced or Edit or Market. Either one of those 3 but click on it and spike those number high

2026-08-04 00:27:48 +00:00

https://gitlab.com/pulsechaincom/pulsechain-mainnet/-/issues/37#note_3639206223
🗿1
PulseChain activity

Bret pushed new project tag v1.1.4 at PulseChain / pulsechain-bridge-server

Bret (0fa3ac9f) (https://gitlab.com/pulsechaincom/pulsechain-bridge-server/-/commits/v1.1.4) at 26 Aug 17:53

Update release version v1.1.4

2026-08-26 17:53:14 +00:00

https://gitlab.com/pulsechaincom/pulsechain-bridge-server/-/commits/v1.1.4
PulseChain activity

Bret pushed new project tag v1.1.5 at PulseChain / pulsechain-bridge-server

Bret (4bce47b2) (https://gitlab.com/pulsechaincom/pulsechain-bridge-server/-/commits/v1.1.5) at 26 Aug 18:27

Update release version v1.1.5

2026-08-26 18:27:48 +00:00

https://gitlab.com/pulsechaincom/pulsechain-bridge-server/-/commits/v1.1.5