[Spike] Pollar Wallet Integration – Abstracted Onboarding + Escrow Deployment

[techrebelgit]

[Spike] Pollar (Polaris) Wallet Integration – Abstracted Onboarding + Escrow Deployment

Summary

We want to explore integrating Pollar (Polaris) into the clonable-backoffice as an alternative wallet onboarding and signing experience.

The goal is to evaluate how a fully abstracted onboarding flow (OAuth → wallet → funded account → ready to transact) could replace or complement the current Stellar wallet integration.

This spike focuses on:

1. Logging in using Pollar (e.g. Google OAuth)
2. Deploying a Trustless Work escrow using the Pollar wallet

This is an exploratory spike, not a production implementation.

Links:
Pollar Docs
Pollar Github

---

Context

The current clonable-backoffice uses the Trustless Work wallet provider (@trustless-work/blocks) and Stellar wallet connectors.

We want to test a different paradigm:

→ No wallet installation
→ No seed phrases
→ No trustline setup
→ No explicit transaction signing UX

Pollar provides a full onboarding stack that abstracts all of this:

• OAuth login (Google, etc.)
• Automatic wallet creation
• Deferred funding
• Trustline setup
• Fee abstraction

:contentReference[oaicite:0]{index=0}

This could significantly improve UX for non-crypto-native users and expand Trustless Work into more consumer-friendly use cases.

---

Goal

Validate whether Pollar can:

1. Replace or sit alongside the current wallet provider
2. Successfully authenticate a user
3. Provide a usable wallet address
4. Be used to deploy an escrow via the Trustless Work API

We are NOT trying to complete the full escrow lifecycle in this spike.

---

Key Questions to Answer

• Can Pollar wallet addresses be used directly with Trustless Work?
• How does signing work for contract deployment?
• Does Pollar support the transaction flow required by TW escrows?
• What changes are required to the current wallet abstraction?
• Can this be modularized cleanly?

---

In Scope

• Install and configure @pollar/react

• Wrap part of the app with PollarProvider

• Implement a Pollar-based login flow

• Retrieve wallet address from Pollar

• Create a separate wallet provider adapter/component

• Use that wallet to:

  • Call Trustless Work API
  • Deploy an escrow

• UI can be minimal (buttons + logs is fine)

---

Out of Scope

• Full escrow lifecycle (milestones, approvals, release)
• Refactoring the entire app to Pollar
• Backend changes unless strictly necessary
• Production-ready UX or styling
• Security hardening

---

Suggested Approach

1. Keep It Modular

DO NOT replace the current wallet system.

Instead:

• Create a parallel Pollar adapter
• Example:
  • /lib/wallet/pollarProvider.ts
  • /components/pollar-login.tsx

Goal: future ability to support multiple wallet providers.

---

2. Minimal Flow

Implement:

Step 1 – Login

login({ provider: 'google' })

Step 2 – Access wallet

• Extract wallet address from Pollar
• Log it in UI

Step 3 – Deploy escrow

• Use existing TW API flow
• Replace signer/address with Pollar wallet

---

3. Integration Strategy Options (Explore Both)

Option A — Direct Replacement

• Treat Pollar wallet as signer
• Plug into existing escrow flow

Option B — Adapter Layer

• Create unified interface:

type WalletAdapter = {
  address: string;
  signTransaction: (xdr: string) => Promise<string>;
};

• Implement:

  • TWWalletAdapter
  • PollarWalletAdapter

---

Expected Output

A successful spike includes:

• Working Pollar login (OAuth)
• Wallet address displayed in UI
• Ability to attempt escrow deployment
• Partial or full success deploying escrow

PLUS:

• Clear notes in PR:

  • What worked
  • What broke
  • Missing capabilities
  • UX implications
  • Recommendation: pursue / not pursue

---

Acceptance Criteria

• Pollar SDK installed and configured
• Login flow working (OAuth)
• Wallet address retrievable and displayed
• Escrow deployment attempted using Pollar wallet
• Code runs locally
• Findings documented in PR
• Screenshots or video included

---

Technical Notes

• Pollar React SDK:

  • @pollar/react

• Uses:

  • PollarProvider
  • usePollar()

Example:

const { login, wallet } = usePollar();

• Requires:

  • Publishable key
  • Testnet configuration

---

Risks / Unknowns

• Transaction signing compatibility with TW
• XDR signing flow differences
• Fee-bump / sponsorship handling
• Trustline assumptions
• Smart contract compatibility

---

Definition of Success

We consider this spike successful if:

👉 A user can log in with Pollar
👉 We can retrieve a wallet
👉 We can attempt or complete escrow deployment

Even if imperfect, we learn enough to decide next steps.

---

Branching & PR Rules

Please do not work directly against main.

1. Create a new branch for this spike:

spike/pollar-wallet-integration

2. Do all your work on that branch.

3. Commit only to that branch.

4. Open your PR into this branch, not main.

5. In your PR description, include:

   • what you changed
   • what assumptions you made
   • what remains unresolved
   • screenshots or short video
   • setup instructions

This is an exploratory spike — insights matter as much as code.

[aleregex]

@aleregex has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I would like to work on this issue because I am part of the Pollar team and already have direct context on the product, onboarding flow, and wallet integration goals.

My experience includes building with Stellar, working on wallet UX, onboarding infrastructure, and developer-focused product integrations. Because I am already familiar with Pollar’s direction, I can contribute quickly and help move this spike forward effectively.

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

[AnoukRImola]

@AnoukRImola has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi guys, lovely day! I'm Anouk Rimola. I'd like to take this one.

I'm a fullstack dev with 5 years of experience. Backend with Node and Rust —
REST APIs, PostgreSQL, Redis, auth flows, background jobs. Frontend with React
and TypeScript. Cloud infra with Docker, K8s, CI/CD. On Web3, I've been
building on Stellar/Soroban — smart contracts, Trustless Work integrations,
and wallet flows.

I've reviewed the codebase and understand the patterns. Happy to discuss
approach in a draft PR if needed. Can start right away 🫡

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

[Villarley]

@Villarley has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hey Alberto! would like to tackle this one, i have reviewed pollar docs and it's a great oportunity for delivering a quality pr.

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

[drips-wave]

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

🧑‍💻 @aleregex: 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 🌊