
The platform consists of several components, which include:
An Android mobile app, named Ben Wallet.
A WebApp, to provide account information and details view on account transactions and account stats, named MyBen hosted on https://myben.xyz.
An RPC server that handles blockchain interaction as well as Launchtube interactions, named BEN RPC.
A monitoring and reporting server to provide timeseries information on the platform's status, as well as consolidated stats, named Ben OpenStats.
An offload-compute server, for part of the farming cycle, so devices can offload compute-intensive tasks, named Remote Grow.
A Kotlin SDK for Android mobile apps, to support building Stellar-based apps on mobile devices.
It is important to highlight that once Protocol 23 is deployed, higher limits will require higher network usage to re-test; the mobile app has the potential to bring additional “test” users (where load comes from real-life interactions).
Complete information on the platform can be found on our live docs: https://ben-wallet.gitbook.io/ben-wallet
Yes
$77.9K
At least 15% conversion rate from Web-based farmer to Ben Wallet, after mainnet launch
3% MAU increase after mainnet launch
Branding-wise: Ben wallet becomes a well known player in the ecosystem.
Kotlin SDK adoption and other mobile apps are made by third parties (or by us) with our SDK.
Our Gitbook serves as a guide for other SCF candidates; meaning, they use our docs structure as a template for their submissions (we think we are on the right track structure and information wise). Standardization would go a long way to help reduce burden of SCF reviewers while conducting reviews.
We don't intend to wait until mainnet to start promoting Ben Wallet, as the advantage of sideloading means early users can try out the app (and platform) even while we are on alpha and beta releases.
Our releases will be published on our github as .apk, and an Installation guide will be provided not only on Github but also on our live docs at: https://ben-wallet.gitbook.io/ben-wallet/help/user-guide
Once we have stabilized at least our mobile application, we would like to promote via socials (mentions on @buildonstellar would be appreciated!) as well as with the team at LumenLoop. We will also reach out to Ambassador groups for amplification, as well as the Stellar Global Discord.
We're basing our initial traction on the one brought so far by KALE, and high-usage of the network by its operations.
Our MVP will focus on the Tractor (harvest) function since it requires the most basic setup for transactions to be made.
This means the following platform components are 1. implemented, 2.tested and 3. released, to the extent of making transactions using InvokeHostFunctionOp:
Kotlin SDK: XDR Module
Kotin SDK: RPC Module
Kotlin SDK: Transactions (InvokeHostFunctionOp)
Ben Wallet: UI 1.0 (Jetpack Compose)
For complete roadmap, check our live docs: https://ben-wallet.gitbook.io/ben-wallet/roadmap
Please note we're trying to keep things simple in the submission, there are many additional sub-components, modules and test runners that are needed for the above. Full details will be published on our live docs https://ben-wallet.gitbook.io/
For our "testnet" tranche we are focusing on deliverables that handle Passkeys and Launchtube.
This means the following platform components are 1. implemented, 2.tested and 3. released, to the extent of having fully featured, alternative to console-miners, mobile application:
Kotlin SDK: Passkeys module
Kotlin SDK: Balances module
Kotlin SDK: Horizon module (evaluate if needed at this point)
Kotlin SDK: Launchtube module
Ben Wallet: Account Management (of C addresses)
Ben Wallet: UI 2.0 (Jetpack Compose)
Please note we're trying to keep things simple in the submission, there are many additional sub-components, modules and test runners that are needed for the above. Full details will be published on our live docs https://ben-wallet.gitbook.io/
For our "mainnet" tranche we are focusing on deliverables that handle the KALE farming cycle.
This means the following platform components are 1. implemented, 2.tested and 3. released, to the extent of having fully functional mobile application, available for sideloading:
KALE ops: Plant (seed)
KALE ops: Work (grow)
Android NDK -> Rust | C++ (evaluate which NDK) for compute-intensive component.
Remote Grow POC (precursor to Google Play Store policy compliance)
Physical and Virtual device tests: Automated & Manuel Firebase TestLab runners.
Note: We're basing our budget estimate of $77,910 on a 3.5 month timeframe, from MVP to Mainnet (all three tranches).
Please note we're trying to keep things simple in the submission, there are many additional sub-components, modules and test runners that are needed for the above. Full details will be published on our live docs https://ben-wallet.gitbook.io/
Team lead: Matias Wald (Discord: waldmatias, https://www.linkedin.com/in/waldmatias)
Muti-disciplinary background (research, business, development) with over +20 years in technology, serving in a wide-array of roles and responsibilities, ranging from Developer to Software Architect, while at the same time managing small, focused teams, to success.
Long-Term Stellar community member and SCF Pilot.

No other submissions.