bAPI

[bAPI]

@tarascadao is welcome. We would like to say that testing is completely unnecessary but it is difficult to be certain. The reality is that your use will be somewhat experimental and would be very helpful if it exposed some flaw in a corner-case. Tarasca DAO could also help us refine the service to better suit their and other’s use.

Please describe Tarasca DAO’s needs and we will attempt a more specific reply with a working scheme using bAPI or adapt the service if that is within our ability and the service’s scope and technical limits.

If Tarasca DAO’s need is an asset bundler then we can already suggest a set of rules.

rule filter set sender type subtype chain id recipient sum_limit transaction_limit user_limit phased message_prunable message encrypted_prunable encrypted message_self

rule filter set * 2 * * card_id1 * 25000 1 500 0 0 0 0 0 0 asset bid, ask, transfer, cancel_bid, cancel_ask
…
rule filter set * 2 * * card_id100 * 25000 1 500 0 0 0 0 0 0 asset bid, ask, transfer, cancel_bid, cancel_ask

or a more limited alternative

rule filter set * 2 3 * card_id1 * 50000 1 500 0 0 0 0 0 0 asset bid
rule filter set * 2 2 * card_id1 * 50000 1 500 0 0 0 0 0 0 asset ask
…
rule filter set * 2 3 * card_id100 * 50000 1 500 0 0 0 0 0 0 asset bid
rule filter set * 2 2 * card_id100 * 50000 1 500 0 0 0 0 0 0 asset ask

These rules set a limit of 50000 lifetime limit per rule, split by ask/bid in the alternative or shared by all asset operations in the first example. There is a per transaction limit transaction_limit of 1 cent which excludes new accounts from using these rules. This per transaction_limit should be increased by 100 cents to allow new accounts to send their first transaction. The ability for a new account to send a first transactions is waiting on a new Ardor platform release. All phasing and message attachments are disallowed to keep the total possible transaction cost to 1 cent. As the rules are configured no individual account can spent more than 500 cents across all rules. These limits are an example, any values could be used.

Tarasca DAO could choose to give some accounts a special status by increasing their total rule limits using rule account limit.

rule account limit sender balance ? transaction_limit user_limit

rule account limit account1 ? ? ? 2500

The account account1 specified would have an increased limit of 2500 cents summed across all rules. ? keeps each rule’s specific limits.

The rule’s sum_limit can be greater than the account’s available balance or this limit could initially be set lower and updated later. A rule’s lifetime sum is reset with each rule filter set command. A set of 1000 rules would temporarily lock 100 ARDR. This balance would be returned as the rules expire or are deleted. There is no additional balance lock for changing an existing rule.

• This topic was modified 2 weeks, 6 days ago by bAPI.

You need to login in order to like this post: click here

[Tarasca DAO]

@bapi
What we need is to be able to bundle for free
1. of the transactions with a MS currency (giftz)
2. of the transactions (ask, bid, transfer) of our cards (assets).
To avoid spam in our private bundler we have put a QuotaBundler of 10 operations per account.
It is not complex, although it is a bit laborious. Also, for some reason we don’t know, sometimes the bundler goes off without warning (and without running out of funds).

My question with the bundler that you propose is: if there are several companies using the same bundler, how do the balances of each differ? For example, Tarasca may load the bundler with 50 Ardor, SmartVoting with 100. At the end of the month, the bundler has paid for Giftz transactions by spending 50 Ardor, but SmarVoting has only sponsored transactions worth 10 Ardor. The bundler still has a balance of 90 Ardor, but if it continues to sponsor Tarasca transactions, it would be doing so at the expense of SmartVoting.
How is that solved?

• This reply was modified 2 weeks, 1 day ago by Tarasca DAO.

You need to login in order to like this post: click here

[bAPI]

Thank you for the question and our apology for the delay in getting back you.

You question regarding the bookkeeping is important. bAPI keeps independent bookkeeping for each depositor and Tarasca DAO cannot spend another’s deposit and vice-versa.

The ARDR deposits are reserved for sponsored transactions. In addition bAPI has it’s own balance for joining sponsored transactions with general user transactions.

At any moment your account balance can be requested by sending an unconfirmed message to @bSTAT which will reply with an encrypted message that includes the active rules and balance spent for each rule since the rule’s last set.

The bundling rules you propose are relatively simple with bAPI. 2. Has been described above. For the currency:

rule filter set sender type subtype chain id recipient sum_limit transaction_limit user_limit phased message_prunable message encrypted_prunable encrypted message_self

rule filter set * 5 5 2 9375231913536683768 * 2500 1 10 0 0 0 0 0 0 currency exchange, no attachments, no new accounts
rule filter set * 5 3 2 9375231913536683768 * 2500 1 10 0 0 0 0 0 0 currency transfer, no attachments, no new accounts

These rules will sponsor currency exchange and transfer from any account on the Ignis chain. There is a 25 ARDR limit per rule and 10 cent per user across all rules. To allow new accounts the per transaction limit transaction_limit would need to be increased by 100 cents.

A general rule can be used to combine the rule limits.

rule filter set * 5 * 2 9375231913536683768 * 5000 1 10 0 0 0 0 0 0 all 9375231913536683768 currency operations, no attachments, no new accounts

This rule has a combined 50 ARDR limit for all 9375231913536683768 currency transactions and 10 cent per user limit across all rules.

• This reply was modified 1 week, 5 days ago by bAPI. Reason: per user limits are across all rules

You need to login in order to like this post: click here

[Tarasca DAO]

Ok, it seems very convenient for us. We will test it for sure, but maybe we are going to wait some more weeks (right now we are fighting an annoying bug and it is our absolute priority).

You need to login in order to like this post: click here

[Author]

Posts