Would you mind explaining the process in detail?
So, we play around 3 things: wallet management, privacy and transaction optimization.
Optimized transaction (best case) = one input + many outputs
Optimized transaction = high economy
For better understanding, let’s imaging you’re going out and taking a hundred bucks for pocket expenses, you know you gonna buy a lot of small thing today
You don’t want to take your nano-ledger out of strongbox for buying an ice-cream and Starbucks coffee
So, our service giving you “a pocket” for regular expenses with discount or cashback as bonus
1 way of usage:Batching Box (our internal name)
Batching Box purpose is to consolidate inputs to achieve the best-case efficiency
Batching Box has time window and volume parameters
Parameters and Batch Box’s amount are dynamically adjusted to match current service load (for example, to not let somebody wait for too long till reach best case)
User receive batching box address to put coins on, this amount became user’s balance
When making payment, the transaction is performed from a random matching batching box and the user receives a transaction which he can share with the recipient
This means, there is no link between your account, your initial batching box and transaction.
If customer wants to withdraw, everything is same, he receive coins from random batching box.
High economy, high privacy, but some users may dislike feeling of “not having a wallet”.
2 way of usage:Personal Wallet (two-steps procedure)
You’re getting a wallet address and a private key that can be imported
When you perform a transaction there are two steps:
1) Wallet -> batching box slow transaction (low-fee rate) to consolidate inputs
2) One-to-many optimized transaction from batching box (another) to recipients
Still high privacy, less economy, but still better (cheaper and/or faster) then single transaction and giving user a control of his wallet
there is no service that can run without a fee, what are your fees for that?
There is still a market niche for such types of solutions, and the goal is to take the place, so there will be no fee for using a service for beginning. Afterwards, most likely, it will be just small percent of the economy of large transactions.
what's this approximate "minimal users" number you're looking for?
Good savings start from batching ~5-25 payments. Let's say 10% (too optimistic) of users will use service once per day - 250 users and I believe we can launch it.
That is a pretty bad way of starting a service.
I would love to choose a better option.
But imagine, user registers on a service to get lower fees, and can’t get it because there is 2 transactions per day.
I suppose 'coming soon' less dissapointing than impossibility to use, while we gather people together.