[Enhancement] Tipping notarization uses `randomBytes` mock txHash instead of a real blockchain transaction

[RUKAYAT-CODER]

Overview

src/app/api/tipping/route.ts generates the transaction hash using randomBytes(16).toString('hex') with senderAddress: 'anonymous' and chainId: 'server'. The notarization proof is a hash of fabricated data, not a verifiable on-chain event. Anyone who verifies the txHash on-chain will find nothing.

Specifications

Features:

• Tips are settled as real on-chain transactions using ethers.js
• The txHash recorded in the notarization record is verifiable on the target network

Tasks:

• Use src/services/serviceAccount.ts sendTransaction() to create a real on-chain transfer
• Replace mock fields with real values: senderAddress = await getServiceAddress(), chainId = network.chainId
• Store the real txHash from the transaction receipt
• Add error handling for failed on-chain transactions (return 502 with retry advice)

Impacted Files:

• src/app/api/tipping/route.ts
• src/services/serviceAccount.ts
• .env.example

Acceptance Criteria

• Tip transaction hashes are verifiable on the configured blockchain network
• Failed on-chain transactions return HTTP 502, not a success with a fake hash
• senderAddress and chainId reflect real network values

[adamualihantsu]

@adamualihantsu has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hey maintainer kindly assgn me to work on your issues

ℹ️ Repo Maintainers: To accept this application, review their application or assign @adamualihantsu to this issue.

[Okorie2000-code]

@Okorie2000-code has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainer, I'd love to work on this issue. I understand the requirements and will submit a clean, well-tested PR. Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Okorie2000-code to this issue.

[drips-wave]

Congratulations, @adamualihantsu! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @adamualihantsu: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[captainjoel2019-bit]

@captainjoel2019-bit has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I’ve reviewed the tipping issue and understand the on-chain transaction requirements. I’m confident I can replace the mocked transaction data with real values and add proper failure handling while keeping the API behavior consistent.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @captainjoel2019-bit to this issue.

[xtrial01]

@xtrial01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I'd like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @xtrial01 to this issue.

[SamixYasuke]

@SamixYasuke has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer,

I can replace the fabricated tipping hash with a real on-chain transaction using the existing service account, recording the actual sender, chain ID, and transaction receipt hash. I’ll also add proper 502 handling for failed transactions and verify the notarization flow end-to-end.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SamixYasuke to this issue.

[drips-wave]

Congratulations, @captainjoel2019-bit! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @captainjoel2019-bit: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊