Polkassembly Logo

Create Pencil IconCreate
OpenGov

Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more

View All Discussion

Treasury Proposal: subledgr - a site for aggregated, cross-chain fund management and reporting

userderekc
3 years ago

Proposer: derek // metaspan


Short description: The goal of the project is to create easy-to-use tools for managing & reporting - in aggregate - across multiple chains, tokens & wallets.

By providing features, and following a style that is familiar to web2 users, this site will drive web3 adoption by making it easy to manage groups of wallets as a single fund or reporting unit.


Requested Allocation: Phase 1: 1730 KSM (~£48k, 1 KSM = £28, 31-jan-2023)


Problem Statement

  • Multi-chain, multi-wallet

    Wallet holders & fund managers do not have affordable multi-chain, multi-wallet tools focused on financial management, reporting and planning.

  • New processes

    There are no solutions providing (aggregated) tracking and accounting for funds locked in validating, staking, nomination pools, lending & governance processes.

  • Lagging tools slow adoption

    Web2 tools are focused on fiat with 2-decimal computation & reporting.

  • Affordability

    Existing crypto accounting tools are charging large fees:

  • Parachains

    None of the existing solutions cater for parachains


Target Audience

  • Project Managers, Curators, Accountants
  • DAOs, Clubs, Societies
  • Fund Managers
  • Businesses using crypto


About Subledgr


Subledgr would like to develop a quickbooks style accounting & reporting platform, integrating with third party vendor tools for the purposes of tax calculation and compliance.


Subledgr would also provide portfolio management and reporting features for working with multiple chains and multiple wallets. We are inspired [and frustrated] by similar features from quickbooks/xero for web2 SME businesses.


Full details and costing available in the draft proposal here:
https://docs.google.com/document/d/15F79YMx5B5qGB3N8AlPD9r7UYW4WcH-AECFNIb6BmnA/edit?usp=sharing

I would appreciate your review and comments (either here or on the draft proposal itself).

Thanks

Comments (6)

3 years ago

Hi Derek, this would be awesome!

Having a "proper" accounting system for crypto assets would be a dream come true... We use one of these commercial crypto-tax solutions mentioned in the proposal and we still struggle to reconciliate across all different networks, different tokens, different decimal places, different API specs, different CSV file formats, too much pain, and it never matches actual balances!

I wish you the best and hope to see Subledgr going beyond substrate-based assets and become the de-facto Quickbooks for crypto.

Regards..

Milos

3 years ago

Hello Derek and thank you for submitting this proposal for discussion! 🌞

Accounting is one area of account management that is often overlooked in this ecosystem, despite being essential to numerous stakeholders (especially Treasury spends recipients!). From that perspective, Subledgr's proposition already looks very promising.

A few comments/questions:

  • From my understanding, Subledgr will be an independent platform/tool that users can connect to with their wallets to have an overview of their account operations for the purpose of accounting. Obviously, this solution will require integration of ecosystem wallets to reach as many users as possible.

Q: Have you already started to liaise with wallet teams about this project? If so, has their feedback informed this proposal, especially since some of them are developing their own Portfolio management tools?

  • One of the features proposed by Subledgr will be the provision of Tax returns/submissions reports. However, tax filling is a process that has many variables and small prints, with each country (and sometimes each state within a single country!) outlining their own requirements.

Q: What kind of information will these tax reports provide to users and on the basis of which jurisdictions? Will there be options for customising these reports?

  • When designing new tools for ecosystem participants, the recommended approach is to conduct as many user tests as necessary to get the best MVP possible, and also deliver maximum value to the community from the Treasury funds received.

Q: Are you planning to onboard ecosystem stakeholders into your developments for testing purposes? If so, will you provide incentives/rewards for their time/contributions?

  • Finally, the proposal document mentioned background information about the project manager (you) and team budgets, but there are no actual team member names. Building a team after receiving funding for a project is common practice, so this is not an issue per se.

C: It might be an option to let community members know if there are open positions in this project, so that they can get in touch if they have the relevant skills/expertise to contribute later down the line.✍🏿

Thank you for your time!

3 years ago

@anaelleltd thank you for taking the time to review and comment.

About existing wallets: I found there is a lack of existing functionality aimed at portfolio managment and reporting. Wallets are not a target datasource for us. We will use the same datasources as wallets - i.e. on-chain data - and combine this with off-chain data (exchange rates, etc) to provide the required features.

I have removed references 'wallet' as I think this could be misleading. We hold funds in accounts - and we use wallets to help us manage accounts.

Tax reporting: for Phase 1 subledgr will provide CSV download function that can be used to feed into the tax submissions - as you say, this area is complex, the needs are different for each country so we plan to tackle detailed requirements in a future phase.

Testing / beta users: this is a great idea, thank you! I'll combine this with the next answer.

Team structure: you are correct, I have not assembled the team yet. I will define technical architecture first, which will inform us what skills are required for the rest of the project. My expectation is that we'll need

  • backend: node.js, javascript, web services, api skills
    • depending on the indexer solution, we may need rust
  • frontend: vue.js, polkadot.js api
  • graphic design
  • testing: we use BDD - which forces us to write user stories and test cases before we write code.
    • beta users, as per you suggestion above - I will add a 'bug bounty' to the proposal.
Load more comments
PleaseLogin to comment

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2025

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy