Focus: Web Trading Experience, Market Data Integrity & Execution Reliability

Brief
Over the past month, our engineering efforts focused on improving the usability, reliability, and execution quality of PinkPunk’s web trading experience.

We introduced a redesigned web interface with a Quick Trade module to lower the entry barrier for non-advanced users, strengthened K-line data integrity under extreme market conditions, optimized Solana execution paths through custom routing, and reinforced core data services to better withstand RPC instability.

Together, these changes move PinkPunk closer to a trading experience that is simpler to use, more trustworthy, and more resilient at scale.

It has been nearly a month since the previous TechLog update.
During this period, we intentionally shifted our engineering focus from feature expansion to improving real-world trading experience and system robustness, especially on the web platform.

As our user base diversified, several patterns became clear:

• A growing number of users prefer simple, fast execution over advanced trading interfaces

• Market data (K-line) readability degrades under extreme on-chain behaviors

• Execution quality on Solana can vary depending on routing strategy

• Infrastructure instability (e.g. RPC issues) can easily propagate to user-facing failures

This month’s work centered on one goal:

Make trading easier to use, easier to trust, and harder to break.

• Most Web3 trading interfaces default to advanced modes

• Users who simply want to “execute a trade quickly” face unnecessary friction

• Sandwich attacks introduce abnormal long wicks

• Temporary data gaps cause visible discontinuities

• Generic routers are not optimal for all DEXs and pools

• Latency and execution precision vary by route

• Node-level instability can cascade into UX and trading issues

Decision

• Introduced a new Web UI design

• Added a Quick Trade module as a simplified entry point before advanced trading features

Rationale

• Lower the barrier for users unfamiliar with complex trading concepts

• Reduce the gap between “wanting to trade” and “being able to trade”

Result

• Fewer interaction steps required to complete a trade

• More predictable and focused trading behavior on Web

Problems Addressed

• Abnormal wicks caused by sandwich attacks

• Discontinuities caused by missing or delayed data

Changes

• Improved aggregation logic to reduce the visual impact of extreme single trades

• Added gap-handling and time-alignment mechanisms for short-lived data loss

Result

• Significantly improved K-line readability

• Price trends are clearer and less dominated by noise

Decision

• Enabled custom-built routing for selected Solana DEXs

Rationale

• A one-size-fits-all router does not yield optimal results across all liquidity conditions

• Custom routing allows finer control over execution speed and price accuracy

Result

• Faster transaction execution

• Actual execution prices are closer to expected outcomes

Changes

• Added protective mechanisms for core data services when RPC nodes become unstable

• Prevented node-level issues from directly impacting upper-layer trading logic

Outcome

• Increased system resilience under adverse network conditions

• Reduced user-facing failures caused by infrastructure volatility

• Trading rebates are now supported on the Web platform

• Integrated seamlessly into existing execution flows without added complexity

Focus: Web Trading Experience, Market Data Integrity & Execution Reliability

Brief
Over the past month, our engineering efforts focused on improving the usability, reliability, and execution quality of PinkPunk’s web trading experience.

We introduced a redesigned web interface with a Quick Trade module to lower the entry barrier for non-advanced users, strengthened K-line data integrity under extreme market conditions, optimized Solana execution paths through custom routing, and reinforced core data services to better withstand RPC instability.

Together, these changes move PinkPunk closer to a trading experience that is simpler to use, more trustworthy, and more resilient at scale.

It has been nearly a month since the previous TechLog update.
During this period, we intentionally shifted our engineering focus from feature expansion to improving real-world trading experience and system robustness, especially on the web platform.

As our user base diversified, several patterns became clear:

• A growing number of users prefer simple, fast execution over advanced trading interfaces

• Market data (K-line) readability degrades under extreme on-chain behaviors

• Execution quality on Solana can vary depending on routing strategy

• Infrastructure instability (e.g. RPC issues) can easily propagate to user-facing failures

This month’s work centered on one goal:

Make trading easier to use, easier to trust, and harder to break.

• Most Web3 trading interfaces default to advanced modes

• Users who simply want to “execute a trade quickly” face unnecessary friction

• Sandwich attacks introduce abnormal long wicks

• Temporary data gaps cause visible discontinuities

• Generic routers are not optimal for all DEXs and pools

• Latency and execution precision vary by route

• Node-level instability can cascade into UX and trading issues

Decision

• Introduced a new Web UI design

• Added a Quick Trade module as a simplified entry point before advanced trading features

Rationale

• Lower the barrier for users unfamiliar with complex trading concepts

• Reduce the gap between “wanting to trade” and “being able to trade”

Result

• Fewer interaction steps required to complete a trade

• More predictable and focused trading behavior on Web

Problems Addressed

• Abnormal wicks caused by sandwich attacks

• Discontinuities caused by missing or delayed data

Changes

• Improved aggregation logic to reduce the visual impact of extreme single trades

• Added gap-handling and time-alignment mechanisms for short-lived data loss

Result

• Significantly improved K-line readability

• Price trends are clearer and less dominated by noise

Decision

• Enabled custom-built routing for selected Solana DEXs

Rationale

• A one-size-fits-all router does not yield optimal results across all liquidity conditions

• Custom routing allows finer control over execution speed and price accuracy

Result

• Faster transaction execution

• Actual execution prices are closer to expected outcomes

Changes

• Added protective mechanisms for core data services when RPC nodes become unstable

• Prevented node-level issues from directly impacting upper-layer trading logic

Outcome

• Increased system resilience under adverse network conditions

• Reduced user-facing failures caused by infrastructure volatility

• Trading rebates are now supported on the Web platform

• Integrated seamlessly into existing execution flows without added complexity