White-Label Platform Update Dear all, I'm glad to introduce newest version

of our white-label API that is currently deploying on our new super-powerful machines. So, what has changed so far?

1. Account Preparation Process

I bet at least some of you have encountered very annoying screen with "Preparing your account" loading indicator on the first launch of the app after installation and also approximately once a month after. This is might have occurred when one of following things happened:
- you've just installed the app and service took time to share it's on-chain subscription with you (aka "perform plan-based subscription allocation");
- service's on-chain subscription expired and it is taking time to get all wallets enrolled to renewed one;

Since there is a limitation of the chain, that allows only one transaction per wallet to be broadcasted at a time, with number of users we had it really took a long queue sometimes to get it done.

Well, this is something we won't be worrying any longer about. Now our API has a brand-new thing called Preheated Wallets. What is that? It is prepared in advanced wallets, already with allocated subscription and all neccessary configuration done. So once you install the app from scratch on your device, you won't be creating a new wallet. Instead, you'll be assigned with one of preheated wallets. API will be always keeping over a thousand of preheated wallets in stock, constantly creating new ones.

2. Re-subscription Improvement

As I said, previously if on-chain subscription expired, it took us plenty of time to renew allocations for all the wallets. We have significantly decreased the time required for that operation and queue is no longer needed — all "preheated" wallets are coming with a preconfigured permission to re-allocate on-chain subscription to themselves, once previous one expires. That allows us to re-enroll wallets almost instantly.

3. Do you believe in magic? We do. Meet PlanWizard.

Maintaining high-quality list of nodes under on-chain plan is a task that usually requires hell a lot of attention and takes a lot of efforts. On one hand, new nodes are constantly appearing on chain, on the other — some nodes are disappearing instead. Not to mention the need of keeping track of their pricing, availability and more. To solve this task once and for all we have released PlanWizard — our ultimate plan-management tool that manages your plan and node-based subscriptions automatically. By defining rules for nodes, you setting criteria for them to be listed on your plan. Once PlanWizard finds a new node that matches it — such node will be added to the plan. And vice-versa, if node does not longer meet requirements, it will be automatically removed.

4. We're going for mass adoption

Building apps for Sentinel is not a privilege, it is a right. To make it more accessible for developers worldwide and promote creation of new apps we will make our API accessible publicly for everyone via RapidAPI next week.

You are great

technical question, I am curious > Since there is a limitation of the chain, that allows only one transaction per wallet to be broadcasted at a time, with number of users we had it really took a long queue sometimes to get it done. isn't it possible to combine all messages you want to broadcast into 1 transaction and therefore reduce the time needed to 6s (time of one block) at max? or are there limitations why it cannot be done that way?

It gonna be too fat transaction that it will fail with timeout

fail with timeout as in, it won't land on chain, or the client will timeout waiting for its confirmation

If someone try to unpack Bagimsiz, can drain that wallet? 🤔 Is it safe from flood & attack? Assume I launch a server to show in Bagimsiz then I'll try to touch it with changed command in unpacked apk. Can I drain supply wallet? 🤔

both options can be there

No, you can't

Great so it's safe from modders

Is it implemented? Or next days?

It's deploying right now. Will be fully functional within next few hours.

Great 👌🏻 Sentinel will be game changer.

Do you think reducing sentinel block time is necessary for better user experience?

I think we will eventually come to it anyway, yes.

Стикер

This is very clear, well written and undoubtedly very well developed. Thank you for this. We go for mass-adoption!

To make it short… When LitRay protocol?

Стикер

I have a business proposal about creating an Arabic Telegram community for your project Who should i DM?