Back to Big Spender
Rejected
Requested:
20.00K KSM

#47 Funding the Virto team

Proposer:
Virto Team
 
in Treasury
Beneficiary:
(20.00K KSM)
1st Jan '23

Proposal Summary (updated)

Feliz aÃąo nuevo! 🎆 I'm Daniel, long time builder in the ecosystem, Senior ambassador, humble fellow of the Polkadot fellowship and team lead of the Virto team of the Virto Network.

This proposal is about supporting us the Virto team(more than a roadmap or specific project), we are a creative and very capable group of individuals with great track record building multiple projects in the ecosystem with funds from the treasuries and Web3 foundation(piggy bank too):

It hasn't been the easiest building this way but we believe developing with the ecosystem funds for the ecosystem is the right way to go specially when creating out of the box solutions in the best Kusama style.

We have several exiting projects lined up for 2023 ready for development with the main theme theme of making blockchain technology extremely accessible to the non-crypto-native 99% of the population.

2023 Projects overview

  • Summa: Substrate Meets Matrix, a lightweight multi-chain capable node extensible with WebAssemply plugins, integrated with Matrix(decentralized communications protocol that powers Element) to interact with Substrate blockchains via the messaging protocol.
    • Summa pallet: A blockchain module to create a tighter integration with Substrate, take on-chain actions based on Matrix events, control Matrix rooms/communities on-chain or seamlessly use Matrix accounts and multiple devices with your blockchain.
  • Hardware prototyping: A limited edition handcrafted wood-leather key ring prototype of a hardware wallet you can lose without fear of losing your funds.
  • Valor: Virto's async lightweight open runtime, the plugin system and developer platform that powers Summa, our super app and hardware wallets.
  • FiDOS Super app: Web application(no special installation needed) extensible with WASM applets, it integrates with merchant's web sites for example and it would include apps to manage your summa node and hardware wallets.
  • Further development and improvements to Sube, Scales, Libwallet and other related projects.
  • Kreivo Parathread: The tokenless sister chain of Virto Network for payments of real-world products and services that empowers local communities with its tax collection system.
    • SwapCash: An initial use-case of a real world marketplace for decentralized on&off-ramps.
    • The Federation: A Fellowship-like ranked collective, an extract of the Local Incentives Protocol that attempts to bring the ambassador program on-chain and turn its members into local leaders that can better represent the interests of KSM/DOT holders.
  • Dot.Builders(new - extra credits assignment): PoC of a ranked collective that would allow teams that are committed to bring long term value to Kusama and Polkadot to have easier recurrent access to treasury funds in an automated way based on their reputation level and previous accomplishments to avoid going through the somewhat inefficient and clumsy process of individual proposals, referenda and the micromanagement culture that results from this kind of process :)

The highlights and priorities for 2023 are Summa and the Hardware wallet as they can have a bigger impact short term. Before rushing out a blockchain with no utility into existence we want to focus on experimenting with different forms of user interaction that result familiar and intuitive to the broad audience. We have been laying down the foundations of a technology stack we believe can tackle the many issues the industry is facing to attract mass adoption without compromising decentralization, trying to make the technology extremely accessible, simple to use, cheap and overall remove as many entry barriers as possible, such as:

  • Abstract blockchain protocols. The average Moe doesn't care about them.
  • Hide away cryptography. i.e. say goodbye to seed phrases.
  • Be familiar. Metaverses, NFTs, Staking, etc. are cool new concepts but intimidating for the 99% of non-crypto savvy population which is our focus(let's first grow the pie!).
  • Speak our users language. Avoid new jargon and words that need explanation.
  • Universal and cheap, don't assume everyone has capable smartphone, knows how to install a browser extension or has good(or any?) internet connectivity.
  • Fear of the unknown. Regardless of the intrinsic security of blockchain, trusting your life's savings to new technology is scary.

The Virto Stack(projects detail)

To serve the use cases we aim for we've gone a long way creating a technology stack from scratch that puts a lot of focus on user/developer experience and very lightweight, simple, power/memory efficient, WASM friendly libraries that can run everywhere, this aids in our long term vision to really bringing blockchain technology to the masses, specially empowering regular users in areas where digitization and technology penetration is low and people might have never heard the word blockchain, there is an opportunity to provide inexpensive hardware and efficient software to connect people to Web3 services.

ℹī¸ Road-map is subject to change, estimates of times and human resources(engineering, design, user research, etc.) are approximate and team members(12+ people) will be dynamically allocated to the right project on a need basis.

Valor

github.com/virto-network/valor

Valor roadmap

Virto's async lightweight open runtime, is a WebAssembly runtime abstraction that based on a target platform selects an appropriate WASM compiler(e.g. Wasm3 in embedded devices, Wasmtime for servers, etc). Using the upcoming "Web Assembly component model" we define or make use of existing host interfaces to expose different capabilities to the plugins that are loaded on an internal registry and are supervised in case plugins were to fail.

An important aspect of Valor is to be developer friendly, have enough tooling and define easy to use interfaces so developers can create new plugins in no time without complications.

Valor architecture

Summa

github.com/virto-network/summa-node

Summa roadmap

Substrate meets Matrix is the implementation of a Matrix homeserver and Smoldot based node developed in Rust that can compile to WebAssembly to run in the browser. The Matrix and blockchain functionality are developed as WASM components running on top of Valor, WASM runtime and message broker that routes incoming messages to the blockchain component and other user provided plugins.

The node is distributed as a lightweight single binary easy to deploy with support for multiple blockchains(thanks to Sube). It is great as a personal cloud and easy entry point for users to the Kusama/Polkadot ecosystems as users only need simple WebAuthN or phone number authentication, it provides encrypted communications out of the box including access to any public Matrix channels(all official communication channels in the ecosystem that are hosted by Parity and the Web3 foundation use this protocol).
Building on top of the Matrix account and device management system means users only ever need a friendly MXID(e.g. @olanod:virto.community) to send funds to a friend, multiple devices are supported and even multiparty signature support in case you want to require transactions to be confirmed with a different device or a hardware wallet. With Matrix built-in Secure Secret Storage and Sharing protocol there is also an out-of-the-box solution for secure account backups and arbitrary user secrets. Finally more functionalities are available when installing different plugins that can turn your node into a decentralized notification system or a personal bot assistant that can sign transactions on your behalf.

Summa arch

Hardware wallet prototype

Wallet prototype roadmap

Hardware development is hard and designing crypto wallets to keep in a cold storage with your life's savings makes things even harder as there are a lot of security considerations in their fabrication that increase their price, but it doesn't have to be that way. At Virto we think there is need for a new category of wallets, small cheap devices that are meant to be carried around without the fear that losing them means losing our funds.

As part of our previous work on the Fido prototype we added support for new kinds of back-ends to libwallet and created a simple device that can be used to confirm and sign transactions with the push of a button. Continuing with this idea, we want bring the Virto Stack to inexpensive and commonly available hardware modules, keeping the "artistic" style(wood+leather for the next experiment) and assemble a limited amount of devices to be given away later this year.

The next iteration of the software would be more complex as we will make several optimizations across the stack to fit Valor and other plugins that effectively turn the device into a Matrix client so it can respond to messages in a chat room(e.g. "please sign this transaction"), we would add support for multi-party signatures, a kind of multi-sig that doesn't require sending transactions to the blockchain, so your device can serve as second confirmation factor or the only factor when transacting with small amounts.

Lastly we want to include, at least in a few prototypes, a LoRaWAN capable chip that allows transmitting small amounts of data over long distances that we would use to test the design of an accurate-enough proof of location protocol useful for location sensitive protocols like LIP(or Encointer). This technology is good in places with bad connectivity where users could broadcast a signed transaction to a nearby station(e.g. kiosk,point of sale,neighbor) that submits the transaction on their behalf.

Fido Primero (We promise next prototypes will be prettier than Fido Primero)

Kreivo

github.com/virto-network/virto-node

Kreivo roadmap

Kreivo means creativity, the best virto(virtue) of Kusama 😉 It's the first implementation of the Local Incentives Protocol, our initial effort to bring the the ecosystem closer to a more general non technical audience by providing a place where people can easily form/join communities to conduct real world economic activities that create utility for the ecosystem tokens, such as setting up marketplaces where local merchants or service providers can make a fair living transacting in KSM, or with stable coins.

LIP focuses on making decentralized local businesses be socially responsible without compromising their profitability, a dynamic tax system enables the collection of resources that empower local communities to become their own autonomous micro-economies as well as the fair usage of collected resources for other common good causes like addressing climate change or inequality among others.

From the start LIP was designed for a token-less, yet sustainable blockchain. We prefer this design as governance is not in the hands of a few VCs or team members and it can bring more value to Kusama and to the commercial communities that struggle to attract value to their tokens. The real value of the network will come from the real world use cases that find their home in Kreivo(and later Virto) that will have the incentive to develop and sustain the common shared infrastructure.

A parachain powered by orml-payments

In practice Kreivo would work in a similar way as Statemine which is built around the pallet-assets and pallet-uniques. Our parachain instead has orml-payments as its core functionality, we built the pallet with the support of a Web3 grant and later brought to a wider audience by successfully merging to the well known ORML community repository. This Substrate module is what makes possible to securely pay for products and services thanks to its built-in escrow-like system with refunds, disputes among other features that also include the dynamic fee collection system that communities will use to generate local and global impact.

Governance

Kreivo/Virto's governance would be delegated to the Collectives parachain in the future where we wish to launch the Trade Association and The Federation, a ranked collective formed by local/regional leaders that serve as delegates of the many DOT holders spread around the globe. Together with the relay-chain's governance the three bodies can dictate the fate of different aspects of the chain.

Some use cases

Decentralized on/off-ramps

Current experience for attracting new users is very poor in the ecosystem as most people have to resort to centralized exchanges that are not easily available in every part of the world and require cumbersome verification processes. Virto team's first show case for the technology is swap.cash, a fiat-to-crypto marketplace that benefits from the payments pallet and built-in decentralized communications to offer a seamless Uniswap-like experience and embeddable Swap API for developers that want to on-board new users to the ecosystem by for example allowing fiat payments to merchants that are payed in a stable coin.

d-commerce

The most compelling use case for Kreivo and Virto in the long term is likely decentralized commerce, which is not just traditional e-commerce plus crypto payments, we see d-commerce as a way to put together under the same roof a universe of composable real-world economies where people trade in a more transparent and fair way that puts users and communities in control, where there are clearly defined rules(in the form of code) on how wealth is responsibly distributed for the overall community's sake, for common good causes and ultimately for the users themselves that are owners of the very same products the use.

FiDOS Super APP

github.com/virto-network/fido

FiDOS roadmap

A decentralized chat-centric super-app for the Web(not an extension), desktop and mobile. It's the go-to graphical interface for "Virto products", same as the hardware wallets it is a Matrix client in disguise with the ability to extend its features with WebAssembly plugins. One can install new applets or teach new tricks(mini overlay applets) from repositories maintained by the community. Over time we will add more official applets and UI components to make it very simple for other users to develop new functionality.

FiDOS App

Scales

github.com/virto-network/scales

Scales roadmap

Making use of type information this library allows conversion to/from SCALE encoded data without allocating an intermediate representation, specially useful when conversion is for dynamic types like JSON.

Sube

github.com/virto-network/sube

Sube roadmap

A client library and CLI for Substrate chains with reduced API(one sube function) and a big focus on size and portability so it can run in constrained environments like the browser.

Making use of the type information in a chain's metadata(powered by Scales), Sube allows automatic conversion between the SCALE binary format used by the blockchain with a human-readable representation like JSON without having to hardcode types for each network. When submitting extrinsics Sube delegates the responsibility of signing the payload of a transaction to an external tool(e.g. libwallet).
Sube supports multiple backends under different feature flags like http, http-web or ws/wss, with the planned support for smoldot.

When paired with Valor, Sube can be exposed as an HTTP API that runs both in the server and the browser and be composed with other plugins to create higher level APIs that a client application can use from any platform thanks to the ubiquitousness of HTTP. We imagine existing centralized projects easily integrating with Substrate blockchains in the server with the option to progressively migrate to a decentralized set-up with the whole back-end later running in the user device(e.g. web browser). More interestingly it can be used for progressive decentralization to give users the the best user experience, a Sube powered application can start being served from a server to have an immediate response and 0 start-up time and since plugins can be hot-swapped, the blockchain back-end can be switched from HTTP to light node transparently without the application code ever realizing, giving our users with bad connectivity and slower devices the opportunity to enjoy the best possible user experience without compromising decentralization.

Libwallet

github.com/virto-network/libwallet

Libwallet roadmap

A lightweight and very portable library with simple to understand and use abstractions that allow creating chain-agnostic crypto wallets able to run in all kinds of environments like native applications, hosted wallets, the browser or even embedded hardware.
We have been adding support for multiple backends and will continue to do so specially for different hardware modules with varying interfaces and architectures.

After adding EVM and Bitcoin accounts support and thanks to the ability of a libwallet client to queue transactions before signing, we imagine interesting cross chain use cases like sending BTC to a bridge and sign a Substrate transaction at the same to avoid the problem of using multiple wallets and multiple confirmations.

Team and costs

The Virto team has been working on an ad-hoc basis in a not very sustainable way, with concurrent members ranging anywhere from 2 to 8 depending on availability of resources. However the pool of team members ready to jump full time in the project to deliver milestones on time is around 12+ people assuming economic stability is guaranteed.

We can count on:

  • 1 team lead (Daniel)
  • 4 Senior software engineers (David, Pablo, Jorge, Stanly*)
  • 1 Expert Devops engineer (Nicolas)
  • 1 Embedded engineer (Johan)
  • 2 Mid-level engineers (Bryan, Gabi*)
  • 1 Junior engineer (Manuel)
  • 1 All in one senior designer (Roberto)
  • 1 User researcher (Edith)
  • 1 Economist (Q.C.)
  • 1 Content creator (Camila)

* needs confirmation.
ℹī¸ More virtuous members can join our next phase of development with enough work for everyone but for now this is a size we are comfortable with given the limited amount of funds requested.

The average monthly cost per person is around 3,000+ USD, a 9 months budget for the team ranges from 324,000 to 378,000 USD.
With the requested 20,000 KSM at a price of 23.5USD/KSM(EMA7) that would equal 470,000 USD, minus 10K of operational costs(infrastructure, hardware wallet materials and equipment) and leaving a 20% buffer to account for price fluctuations, missed deadlines and other (un)expected circumstances we are left with 368,000 USD. Worst case scenario if things don't go as bad as usual, there will be extra funds to bring some more awesomeness to Kusama.

EDIT: more info on the team budget and how it compares to market salaries in this spreadsheet.

A note from experience, since we are in the wild west I think exact budgets don't work(hence the beautiful rounded 20K KSM), we have always lost money, sometimes more than 30% of received funds, we made mistakes and learned a lot but it hasn't been because of financial ineptitude but because building in the crypto space is tricky, a lot of times it's crazy price fluctuations but it can also be due to swapping funds to a not-so-stable stable coin for example, a lot can happen! ... a few thoughts on the topic.
Hopefully Kreivo can make payments for projects and services more convenient 🤞

Show More

Proposal Failed

The approval was lesser than the threshold for this track.
Summary
Failed
34.5%Aye
AyeNay
65.5%Nay
Ayes(124)
6.29K KSM
Nays(140)
11.95K KSM
Support
5.24K KSM
Issuance
15.92M KSM
Voting Details
Approval0.00%Threshold0.00%
Support0.00%Threshold0.00%
Please Log In to comment

14Comments
HERT...afdU
 
 
1st Jan '23
Voted Abstain

Is there another discussion page for your request somewhere? I'm having trouble understanding the text above and I don't see a link to a proposal anywhere.

Edit:

I can understand your frustration, that you're trying to secure funding for your team for a period of time, without creating many individual proposals for each smaller project. I would suggest you create a comprehensive proposal detailing your team members, links to their bios, salary requested, and then go into detail on the sub projects (I'm not familiar with any of them) along with linking team members to the projects they're working on and what their commitments to those projects is. I think your proposal is very light weight for the amount of funds that you're requesting. I would expect a more formal document.

I'm abstaining for the moment.

Hide replies
EvoL...oVus
 
 
2nd Jan '23

Hi! Kreivo's post would be the initial discussion, sorry we were missing the projects summary in the initial post. We will be adding more details soon but I'm glad to answer any questions in the meantime :)

HyLi...Hqmx
 
 
2nd Jan '23
Voted Nay

The amount you're asking seems obscured by leaving it in planck. Are you asking for 20,000 KSM? (GBP 375,000)

Hide replies
EvoL...oVus
 
 
2nd Jan '23

Correct! 20,000 KSM to sustain a team of 10+ people(mostly developers) for almost a year ;) There doesn't seem to be a way to tell Polkassembly to show amounts in KSM instead of plancks, it would definitely be a nice to have feature 🤔

GU77...c9Qw
 
 
2nd Jan '23
Voted Abstain

I voted abstain for the moment. While I generally appreciate proposals for building interesting contributions, I find it hard to understand what this one is about, even on a high level. Since it is for a rather large amount, it would help to provide a more detailed document (google doc, hackmd, ...), like most other proposals did.

In addition, this team seems to have a long track record of building in Dotsama with treasury funds. This can be a very good thing to convince people if one gets a clear overview of what has been built, with access to github/gitlab repos, functional or demo apps/sites, ...

Hide replies
EvoL...oVus
 
 
2nd Jan '23

Hi! thanks for the feedback, we will expand on the level of detail of the proposal to make it clearer how the resources will be allocated and try to make it clearer what is it that we are building :)

EvoL...oVus
 
 
2nd Jan '23

Voted Aye

Thanks to those currently supporting us and for those still hesitating, based on the interesting recent conversation at Attempts at governance we hear your concerns, our current approach with the proposal was to present the Virto team and its history building in the ecosystem as a way establish the trust needed to support this kind of spending and ensure you we are here to build for the long term. We still want to make the spending about supporting a very capable team instead of a roadmap but worry not, we will be expanding and adding more details to the proposal to describe how funds will be allocated for those of you that need a bit more truth, also very open to answer any questions and engage in conversation in case it's still not clear what the team is trying to accomplish :)

EDIT: More information on the projects, timelines, milestones, budget have been provided. Hopefully it's also clearer now what are our goals and the technology we are trying to build.

D6Sc...G3wo
 
 
3rd Jan '23

Voted Aye

I have voted in favor of this proposal. And while I adhere to the spirit of more information being required (or better organized in this referenda) for such a proposal, I have a bit more information on the project which I wanted to share. The way I found out about Virto was while doing a Polkadot hackathon, in which Olanod/Daniel, and many others, presented projects as an opportunity for people to try to understand Substrate.

The reasons I've voted yes are the following:

  1. The same reasons I got interested in what Daniel said at the time of that hackathon, which was when this project was on a less advanced stage. A tool being used to aid local markets economies, maintaining resources locally, is something that resonates with me, and probably with most Latin Americans that have seen firsthand the potential p2p markets have on improving economies often hit by the availability of external products with obscene technological advantages. Additionally, the technology stack seemed reasonable to me, leveraging tools like Matrix and not focusing on a project token, imo it aligns with the spirit this type of project needs to succeed. More seems to be available on that here: https://kusama.polkassembly.io/post/1520
  2. Since I first learned about them over a year ago, the project has advanced quite a bit, integrating people and evolving its codebase. We have seen how many projects have been pushed solely by the greed of their native tokens mooning. We can at least know that the growth of this project is mostly related to their team and objectives rather than the potential explosion of a native token, which is not a small feat for a more community-oriented project.
  3. Olanod. During the brief moment I talked with him, he was always available to help people on understanding the project, with great patience. I've participated in quite some projects, and this is certainly not always the case. He is clearly passionate about it both technically and conceptually, and the people working there seemed to be in the same boat.

These are, of course, very subjective points. But I hope they push people to give a bit of extra effort into reading the additional content provided (and updated/edited) by the Virto team.

Hide replies
J9nE...dwcv
 
 
3rd Jan '23

Thanks that helps, having some visibility into this. You got my vote.

dashboard profile icon
qsita
 
 
4th Jan '23

This hardware wallet idea sounds very cool to me, seems as long as you have a matrix account, you could use this wallet and there can be also interactions between different accounts, which reminds me a bit of wechat wallet used by vast majority. If I understood correctly, this potentially could offer a solution to people who don't understand much block chain tech but want to have a user friendly wallet.

I met Daniel in person in Amsterdot event last year. His team has been very down to the earth in their working. They have my full support. I noticed more details about the project haven been added yesterday for more clarity based on provided feedback. For those who vote big no now, I would be also curious to know the reasons here, guess the team as well, which can also give the team more ideas about how to improve.

Come on Virto Team! big fan.

FLKB...svZR
 
 
4th Jan '23

Voted Aye

Hola Daniel ! I voted Aye with 2x conviction because I see you now added the team structure with how much they'll each be paid and I think it's a fair amount for what you're building. Good luck with the referendum & the project if this passes.

HqRc...fVZn
 
 
4th Jan '23
Voted Nay

Hey Daniel,

Given that votes are now inconsequential I'll save myself some hours of DYOR and maintain an minute Nay. I was in the process of doing some research into your past proposals and wanted to get a gauge on their outcome and readiness/completion. There are other reservations but instead of making this into a long and time consuming post I'll just leave things where they're at.

Where I got to so far..

Fido - 69,750 USD https://polkadot.polkassembly.io/motion/246

Sube v1.0 - 20,000 EUR https://kusama.polkassembly.io/post/616

Libwallet - 28,800 USD https://polkadot.polkassembly.io/motion/148

We built the pallet with the support of a Web3 grant and later brought to a wider audience by successfully merging to the well known ORML community repository

I wish you all the best and hope that the funds are utilized well.

Regards,

Hide replies
EvoL...oVus
 
 
9th Jan '23

Adding for completeness. The links here are available in the first part of the post also links to repositories. The W3F grant to develop orml-payments pallet was 36,000 kUSD https://github.com/w3f/Grants-Program/blob/master/applications/lip_payments.md

HERT...afdU
 
 
7th Jan '23
Voted Abstain

We're abstaining for the moment. Waiting for Daniel to provide better documentation of the actual proposal of funding the team to the public per twitter conversations. Additionally, comments were made that our vote is stifling debate on the proposal and that it's unique since it's the first to fund a team and deserves more debate.

HyLi...Hqmx
 
 
10th Jan '23
Voted Nay

We should have this debate about funding a team vs. funding an initiative.

I get Daniels frustration, it's hard to build a team and keep them together if there is no runway of funding.

On the other hand, the community seemed reluctant to sign of on $400k without clear understanding on how this will be used to further the ecosystem.

I think the addition of detail above goes a long way towards providing the missing info.

It's not clear if the previously funded projects are complete, or up to a useable standard. What proportion of this referenda will go towards this?

Hide replies
EvoL...oVus
 
 
11th Jan '23

I would also be very interested to hear more thoughts from the community about funding teams vs specific projects, IMHO I don't think is very sustainable to go the funding per project route, it's ok for getting started in the ecosystem but not for continued development. Instead I imagine a more decentralized future when Parity is no more, individuals in the fellowship focus on very core topics of the protocol but then multiple small-medium sized teams(a.k.a. mini Parities) that are funded by the treasuries focus on building all kinds of surrounding technology like "grass-roots chains", other must haves and initiatives that bring extra value to Kusama and Polkadot.

About the funding and previous projects, except for the Fido PoC that we are wrapping up this month, they have all been completed as expected, the easiest one to verify is the W3F grant as it wouldn't get the completed state without W3F's due process of review. Sube, Scales and Libwallet also were developed as expected, even showed cased last year in the Substrate seminar but as software is always evolving we continue working on said libraries to make them simpler to use, have new features, be more performant and stable. It takes time to take this kind of developments from scratch to a production state(specially when dealing with funds) where it can be recommended for mainstream application building. With the requested funds we will allocate a small fraction(e.g. 10%) to improving this building blocks.
That leaves us with where are most of the funds going to be allocated? Mostly in our Matrix<>Substrate integrations. The Summa node(Extensible Matrix server+Blockchain node) which is a completely new development and the extensible Matrix client in the form of a "Super app" and the new hardware wallet prototype.

Czbc...vCU3
 
 
11th Jan '23

Voted Aye

My fellow community members, I'm David Barinas and I stand before you today as a man on a mission. A mission started nine years ago when I met my friend and business partner, Daniel, in my hometown of Tunja, Colombia. We discovered a shared passion for using technology to impact the world positively. We embarked on a journey to create products that would improve people's lives in our region, using cutting-edge technology like blockchain and web3.

Through our venture, Valiu, which graduated from YCombinator in the Summer of 2019 and raised 5.25M USD, we helped over 350,000 families in Venezuela to receive and preserve their money's value using bitcoin and blockchain technology. This experience was one of the most rewarding of my life. It reinforced our belief that technology can change people's lives and showed us that when we put our hearts and minds into something, we can make a difference.

This is the reason that drives Virto, our team, and me. We understood the importance of simplifying the complexity of blockchain and web3 to create products that bring real value to people's lives. We want to bring blockchain and web3 technology to the masses and truly impact our society. It is a challenge, a difficult task, but we are not afraid. We have made difficult sacrifices to focus on this mission. We have left our jobs and reduced our expenses to pursue this vision because it is possible to change how society works by using technology to benefit people.

This mission is not for the faint of heart and is not motivated by financial gain. We need the support of our fellow community members to make it a reality. With your help, we can change the world and create a better society for everyone. Join us in this mission, and let us be the change we wish to see in the world. Together, we are unstoppable. Our work towards making blockchain technology more accessible to the masses not only helps to improve people's lives but also contributes to the growth and development of the Kusama ecosystem. We help attract daily users and masses, which creates wins for validators and increases demand for native tokens, leading to a stronger and more successful ecosystem for all.

GP7L...po99
 
 
12th Jan '23

Is this what you are building?

https://virto.network/docs/whitepaper

Why do you need an economist on staff?

Hide replies
EvoL...oVus
 
 
12th Jan '23

Hi! sorry you changed your mind :'( Yeah the first implementation of the Local Incentives Protocol whitepaper draft is the parachain Kreivo(some day Virto in Polkadot), it's our main bet to empower local communities with their own autonomous micro-economies fueled by its taxing system that aims to maximize fairness and wealth distribution. That said, implementing LIP is one fraction of our team's focus, our target audience being the non-crypto-native in development countries means we are also spending a great deal of energy on making blockchain technology usable by the masses(integrating with the decentralized communications protocol Matrix).

Out team's economist who has been with us from the start and co-wrote LIP's paper, although more of a support role(as detailed in the budget spreadsheet) is a key part of the team, will help us refine and update the whitepaper plus other documentation related to Virto's economics, will make sure the game theory behind the implemented protocols and different configuration parameters of the chain stay sound(after all we are trying to flip tax systems on their heads) and as it's common in startups support with multiple extra activities to run the team like being our treasurer, a project manager and data analyst to drive decisions.

Glad to chat more and clarify any other concerns that might help you change your mind again about Virto :)

EFgD...f71c
 
 
13th Jan '23

Hey everyone! I am Pablo Dorado, part of the Virto team.

For years, I've acknowledged technology's tremendous impact on improving lives. Mine and the lives of hundreds of people I've met are witnesses of that effect.

And for that, I've always had the enthusiasm for being an agent of change for myself and the communities around me. Whether it's creating tech solutions that positively impact conflict victims, developing accessible products for disabled people to enter college, or mentoring newcomers. Also, the concept of creating groundbreaking stuff is fascinating, and that's why maintaining OSS and living off it has been a lifelong goal.

I met Dani three years ago in a meetup where he introduced us to Substrate. It was refreshing to see an example of the tech ecosystem, where people are encouraged to follow dreams for the benefit of others instead of fighting against the wild forces of the market.

Historically, technology itself has tended to change the tune of human conversations. We've seen it with social networks. The rage behind a strong-worded comment. The rain of emotions. The dehumanisation of the person on the other side of the screen.

Last week, team meetings felt more like being in the HQs of a political campaign. And that's been distressing since you usually expect to be focused on creative and innovative work. As a person with a background that makes us used to submitting a proposal and waiting for opaque deliberation, the concept of governance is new to me.

Still, our spirits remain hopeful that with the power of good argumentation, we'll be able to show our proposal is solid. That's why we agree to keep encouraging debate.

Despite the few comments on the proposal, the debate has been quite substantial, with many questions: the funds we're requesting, the track of prior work, and the colossal team behind it.

That's why we like to invite you to a livestreaming session we'll be holding later today at 11:00am PT / 3:00pm ET / 8:00pm CET on Twitch. Let's meet there to solve doubts, and if you are up to it, engage in a healthy debate with whoever wants to join the session.

E5qF...tqrg
 
 
24th Jan '23

We once again discussed this proposal this week on AAG #19 đŸĨš feat. new important context from the pannel and the team.

👉 https://twitter.com/TheKusamarian/status/1617690573569429504


Discover similar proposals


#508
KSM

Remove Gabe from the fellowship

Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.

See More

24th Mar '25

Fellowship Admin

Fellowship Admin

#508 Remove Gabe from the fellowship
KSM
24th Mar '25

Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.

Invarch failed to provide the first two, so Gabe, a founding member of the team, does not meet the ethical standards required to have a voice in the Fellowship.

TENETS (extract from the fellowship manifesto)

"Members are expected to faithfully uphold the following tenets.
Clarifications to the rules should be in agreement with these tenets. Acting in clear breach of these tenets may be considered by voters as grounds for non-promotion, demotion or, in extreme cases, exclusion from the Fellowship.


(1) Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it.
(2) Respect the philosophy and principles of Polkadot.
(3) Respect the operational procedures, norms and voting conventions of the Fellowship.
(4) Respect your fellow Members and the wider community"

See More

#509
Jay Chrawnna
Deciding

KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!

See More

24th Mar '25
75%

Treasurer

Treasurer

#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
Jay Chrawnna
24th Mar '25
75%

This RFP was adapted over several weeks on AAG to turn a treasury proposal in discussion to an RFP with refined scope and oversight.

To apply for the prize pls fill out this form.  


Prize Pool: $43,000
Finder’s Fee: $2,000 **
Supervisors: $5,000

Supervisors (Bounty Curators)

  • Flipchan
  • Byte (Erin)
  • James Slusser

Excess or unused funds will be returned to the treasury by Bounty Curators.

Timeline

Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators âœ…
4 Weeks after Bounty Funding - Submission Deadline Thursday
July 31 - Project Completion (Pending Kusama Hub Launch)

Project Scope

Smart Contract Development

  • A Solidity-based smart contract deployed on Kusama Hub
  • ZK enabled for private deposits & withdrawals
  • Compatibility with all Kusama Hub assets

User Interface

  • Browser-based, mobile-ready UI hosted on IPFS
  • Support for: Deposits, Withdrawals, Transfers, XCM Transfers
  • Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)

Anti-correlation Attack Mitigations:

  • Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
  • Batch payouts for withdrawals to multiple users
    Interoperability
  • Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.

Open-Source Delivery

  • All code (smart contracts and UI) published under the MIT license
  • Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
  • Developer & User documentation

Milestones

Milestone 1, Initial Pools & Basic UI:
$16,200 USD
1 month

  1. Tests - Smart contract test
  2. Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
  3. Basic UI - A basic UI for interacting with the smart contract

Milestone 2, UI + XCM:
$9,900
1 month

  1. Tests - tests for all features
  2. User interface design - UI design
  3. XCM transfers - XCM transfer assets in UI
  4. Fixed amount transfer only - Allow fixed amount transfers in the UI

Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months

  1. Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
  2. Public documentation - Documentation for using Kusama shield and developer integration documentation
  3. Test - tests for contract
  4. V1 UI - User tested & something we can be proud of

** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.

See More

Deciding
#510
KSM

Secure Funds

To prevent potential mismanagement of Youdle DAO treasury funds, we propose temporarily transferring these assets to the Kusama Treasury, which is now the safest option.

See More

4 days ago

Root

Root

#510 Secure Funds
KSM
4 days ago

To prevent potential mismanagement of Youdle DAO treasury funds, we propose temporarily transferring these assets to the Kusama Treasury, which is now the safest option.

Rationale:

The Invarch team, which currently controls the funds, has a history of questionable financial decisions, including the transfer of more than 200K ASTAR from the DAO to a CEX without transparency.

Community members have raised concerns and asked questions about fund management, but the team has not provided clear answers.

To ensure responsible management, these remaining funds (400 KSM) should be safeguarded under Kusama governance.

Next Steps:

The funds will later be returned to Youdle DAO holders through a transparent and verifiable process.

 

We urge the community to support this measure to protect DAO resources.

 

Evidence:

Rug on virtuals

image.png


image.png

 

Polkadot treasury rugs

image.png

 

Youdle DAO rug

Moving DAO funds to a CEX because it's a shared address instead of moving to another on chain address? No answers. 

image.pngimage.png

image.png

Pink rug

Pink distributed by the pink team to invarch was supposed to get distributed to the community

image.png

but instead 2000000 pink were allocated to xcastronaut (invarch founder) wallet

image.png

image.png

Then went to hydration and got sold.

VARCH rug

$VARCH token launched less than 30 days ago. ICO investors are down -96%
image.png


KSM partial rug

Not fully delivered. 

image.png

Tinkernet rug

Tinkernet (kusama parachain) was shutdown. Investors were given 4 VARCH for 1 TINKER. VARCH was later a rug so this converts Tinkernet in a rug. Before shuting down they made an LBP in Osmosis (Cosmos) which also was a rug. 



See More