WebisoftWebisoft
Scope of Work
Midnight × Webisoft
Resource Allocation
Three scoped paths to keep Midnight Passport moving while restoring momentum on 1am and the wider Midnight ecosystem — with capacity, hours, and priorities managed transparently.
Contact Utkarsh Varma, Webisoft Technologie Inc.
Where the retainer goes today
Current State
The retainer's allocation today is absolute. Utkarsh is fully committed to Midnight Passport — architecture, integration, security review, and the weekly cycle of integrating deliverables from Dynamics, SIG Network, and the identity team. Alvaro is fully committed to the 1am wallet, where delivery has been steady throughout.
Around the retainer, William drives 1am's security posture — auditor conversations ahead of funds going on chain, and the focus that keeps Fast Sync a differentiator no other wallet has — and authored one of the candidate proof-server approaches now awaiting convergence. The Passport working group is Utkarsh (Webisoft), Hector (SDK direction), Carmel (project management), and Nicholas (Shielded — contracts and account management).
The Dynamics-based demo works today. The SIG Network path is blocked on ECDSA and contract-to-contract calls, which are live on Stagenet and expected in preview in August.
Utkarsh Varma
WebisoftLead engineer
- Architecture
- Integration
- Security review
- Passport SDK
Alvaro
WebisoftEngineer
- Wallet delivery
- Feature releases
William R Marchand
WebisoftTechnical lead
- Audit prep
- Fast Sync
- Proof-server design
Kept moving
- Passport demo on the Dynamics path — working today · Utkarsh
- Passkey plus Dynamics dual-path architecture decided
- 1am wallet — steady delivery · Alvaro
- 1am security posture and auditor discussions · William
Stalled or waiting
- Offer files — new UI not started
- Mobile SDK — idea stage, unscoped
- Proof server — three approaches authored (William, Ben, Ricardo), no converged decision
- 1am audit plan and monthly feature cadence
- The in-between projects the partnership used to ship
The bottleneck is structural, not individual: one engineer absorbed a program. The rest of this document staffs Passport properly while returning capacity to every other workstream.
What holds under every option
Restructure Principles
Five commitments that hold under every option.
Split the UI from the SDK
Two separate workstreams with an architecture document that draws the line. After Token, the UI can be embedded into any wallet — including 1am — while the SDK stands alone as the foundation other teams build on.
Scoped lead capacity
Utkarsh remains Passport lead within a defined share of his time — targeted at 25 to 30 percent — reported weekly and reviewed monthly. A number, managed, not an open-ended commitment.
Componentize the SDK
Webisoft anchors on Wallet Storage as its owned component. Every other SDK component becomes an independent folder in the repo with its own ticket and definition of done, so contributors from Webisoft or the Foundation's network can pick one up directly.
Passkey-first, vendor-second
Passport must survive any single vendor going down. A passkey always exists; Dynamics is one wallet option, not the foundation. The architecture reduces the hard vendor dependency over time.
More bets than one product
The retainer returns to funding a portfolio: Passport, 1am, and the ecosystem backlog in parallel — so results keep landing even when one track hits a blocker.
Pick one — each is complete on its own
The Three Options
Each option is complete on its own: a capacity model, a monthly cost, and an explicit trade-off. Option A is recommended; Option C requires no new budget.
Option A — Add a third engineer
Recommended+1.0 FTE
- Utkarsh — Passport lead, Wallet Storage, review~30%
- Utkarsh — 1am and ecosystem backlog~70%
- New senior engineer — Passport delivery100%
- Alvaro — 1am wallet100%
Monthly
$60K / month
Term
3-month initial term
A senior engineer — target profile: Midnight background, SDK experience — onboards over two to three weeks and absorbs roughly half of the current Passport load. Passport keeps its velocity and gains a second reviewer on security; the freed lead capacity restarts the ecosystem backlog; the single point of failure is removed.
Option B — Fractional third
+0.5 FTE
- Utkarsh — Passport lead and delivery~50%
- Utkarsh — 1am and ecosystem backlog~50%
- New engineer — Passport, half-time50%
- Alvaro — 1am wallet100%
Monthly
$50K / month
Term
3-month initial term
Half the backfill at half the incremental cost. Passport holds most of its pace and half the lead's time returns to the ecosystem. The trade-off: onboarding a half-time engineer into a system this complex is slower, and the ecosystem restart is meaningfully more gradual than Option A.
Option C — Reallocate within two
No headcount change
- Utkarsh — Passport, scoped and managed~30%
- Utkarsh — 1am and ecosystem backlog~70%
- Alvaro — 1am wallet100%
Monthly
$40K / month
Term
Ongoing · review at 3 months
No new budget and no approvals — the current retainer, reallocated transparently. The ecosystem restarts immediately, but Passport drops to roughly a third of its current capacity. Viable only if externally sourced contributors pick up the componentized SDK tickets; otherwise Passport pace visibly slows ahead of Token.
Current allocation: one engineer fully on Passport, one fully on 1am, nothing else staffed.
Utkarsh Varma
Lead engineer
Alvaro
Engineer — 1am
Percentages are planning targets, reconciled against actuals in the weekly hour report. The exact Passport share is fixed at kickoff.
Side by side
| Criterion | Option ARecommended | Option B | Option C |
|---|---|---|---|
| Ecosystem backlog restarts | Yes | Partial | Yes |
| Passport keeps current velocity | Yes | Partial | No |
| Removes single point of failure | Yes | Partial | No |
| Second reviewer on Passport security | Yes | Partial | No |
| Incremental budget | +$20K / mo | +$10K / mo | None |
| Requires budget sign-off | Yes | Yes | No |
| Onboarding period | 2-3 weeks | 4-6 weeks | None |
| Lead time on Passport | ~30% | ~50% | ~30% |
Commitments that hold under every option
The Passport Plan
Structural commitments that hold under every option — the difference between a demo that survives Token and a foundation other teams can build on.
UI / SDK architecture document
Defines what is UI, what is SDK, where the boundary sits, and how the UI embeds into other wallets after Token. Written first: every delegation decision depends on it.
Wallet Storage as Webisoft's anchor
Wallet Storage is the first component on the SDK roadmap. Utkarsh owns its design, delivery, and review regardless of who builds the surrounding components.
Componentized SDK repo with tickets
Every other SDK component becomes an independent folder with its own ticket and definition of done, so contributors from Webisoft or the Foundation's network can pick up bounded work without a handover call.
Passkey-first key handling
A passkey always exists; Dynamics is one wallet option, not the foundation. A browser-storage key-handling issue was identified this week before reaching production; its remediation is the first item under this workstream, with structured security review on every change going forward.
SIG Network path to done
The Dynamics demo path works today. The SIG path completes when ECDSA and contract-to-contract calls reach preview — live on Stagenet now, expected in August. Integration work is sequenced to land immediately behind the platform release.
| Capability | Approach | Status |
|---|---|---|
| Dynamics demo path | Working today | Working |
| SIG Network demo path | Awaiting ECDSA + contract-to-contract calls in preview — expected August | Partial |
| Passkey-first key handling | Architecture decided; browser-storage remediation is the first deliverable | Partial |
| UI / SDK architecture document | First deliverable of the restructure | Planned |
| Wallet Storage SDK | Webisoft-owned anchor component, sequenced behind the working demo | Planned |
| Componentized SDK tickets | Independent folders and tickets for delegation | Planned |
What the freed capacity buys
Beyond Passport
The workstreams funded by the freed capacity, pending final ordering in the merged priority roadmap.
1am wallet
Formal security audit before funds are on chain
Auditor discussions are underway; this workstream selects the auditor, fixes the scope, and sets the target date.
Security plan with dates
Audit first, then the open-source decision with target dates. Open-sourcing remains under evaluation; the plan states the position explicitly rather than leaving it open.
Monthly feature cadence
Visible monthly releases that keep 1am ahead of the field and give users a reason to stay.
Keep the Fast Sync edge
Fast Sync exists because the team is focused; the release cadence is designed to protect that focus, not dilute it.
Proof server
One proposal, not three
Three candidate approaches exist, all requiring protocol or ledger changes. A joint task force converges them into a single recommendation for Shielded — replacing uncoordinated parallel effort.
Ecosystem backlog
Offer files — new UI
A rebuilt UI, scoped and scheduled in the merged priority roadmap.
Mobile SDK
Scoped once the Passport SDK componentization proves the delegation model.
Deferred: IDC / IBC connector
Not feasible today: it depends on a Midnight light client, which does not exist yet — the consistent conclusion of the research on both sides. The proposal returns to the roadmap if and when a light client ships.
How the restructure stays visible
Governance & Reporting
Four lightweight mechanisms, all starting in week one.
- 1Week 1
Step 01
Merge the priority lists
Webisoft and the Foundation each contribute a prioritized item list; the merge becomes the single formal roadmap the engagement reports against.
- 2Kickoff
Step 02
Fix the number
The Passport share of lead capacity is agreed at kickoff — targeted at 25 to 30 percent — and becomes the managed commitment every report reconciles against.
- 3Weekly
Step 03
Report hours weekly
A per-workstream hour report lands before the weekly sync, showing exactly where the retainer goes.
- 4Monthly
Step 04
Demo monthly, review quarterly
Every month, a visible demo from at least one non-Passport workstream. Every quarter, the option itself is reviewed — scale up, hold, or restructure.
Next Steps
Four steps to turn this from a document into a running restructure — the first two can begin immediately.
Exchange the lists
Webisoft submits its prioritized item list; the Foundation returns its own. The merge becomes the formal roadmap.
Select the option
Confirm the budget path. Options A and B trigger the candidate search immediately; Option C starts the reallocation the same week with no approvals needed.
Hold the Passport delegation session
With the Passport working group: Wallet Storage ownership, the component ticket structure, and the UI / SDK architecture document as the first deliverable.
Start the clock
Onboarding or reallocation begins within one week of sign-off. The first weekly hour report lands before the next sync.
Direct contact: utkarsh@webisoft.com
Webisoft · Montreal, QC · webisoft.com
Confidential — Midnight Foundation · Resource Allocation — Statement of Work
Webisoft · Confidential
Midnight × Webisoft
Resource Allocation
Prepared for the Midnight Foundation. Enter your email to view the proposal.