Well, for the metrics that we measure are actually quite standard with what is usually done by many other products. But to provide more clear information here are some of the metric we’ll pay attention to when doing stress tests are as follows:
Hope it answer ur question!
1 thing that I am observing is that you respect user privacy, but how are you going to make sure that all of your anonymous testers are going to test all the critical features, thank you
Oh yeah, that absolutely answers my question. It’s great to hear that you’re focusing on important metrics like TPS, latency, and scalability during stress tests.
In my own opinion, this is really crucial for ensuring you can handle high volumes of transactions and provide a smooth user experience.
What is the minimum acceptable TPS under stress conditions? And, will your stress tests include testing for possible security breaches or vulnerabilities that might arise during periods of high load?
I had to go get back to this. Are you going to give users the chance to select the duration of wallet being inactive or you are going to provide some time for users to select from?
Hi @ines_valerie , For the testers that we invite, we have prepared test case scenarios that will cover all the critical features.These scenarios will guide testers step by step through the platform’s key functions, ensuring that each aspect of the system is tested, from basic transactions to more complex use cases such as scheduled transfers and failover scenarios.
After the tester has complete all the test case scenario, We will invite testers to participate in a beta testing phase where they will be asked to provide structured feedback after testing certain critical features. This feedback will give us insights into how the features performed under real user conditions and help us identify areas that may require further improvement before the final release.
For this first iteration MVP release, we expect to handle 30 TPS. Although this number is quite low, we have projected further development for the scalability of our platform in order to increase our user base.
During the stress test we also included some testing for false transactions to see how the system responds. However, we do not have the capability to test for cyber attacks at the moment. But of course we will try to be able to test that too in the future.
Due to the limitations of development in our first iteration, for now we only have the capability to provide the exact time that has been determined by us beforehand. But of course we will make improvements in the future in order to provide flexibility for our users
So now what’s the time. 3 months?
Welcome to Tron hackathon season 7 team malink i like the idea behind your project because a whole lot of people have lost funds either by forgetting their seed phrase or by misplacing their devices.
I also like the concept of scheduled transfer and recurring payments. Let’s say I schedule a transfer for a couple of weeks earlier what happens if the blockchain network faces congestion or high gas fees when a scheduled transfer is supposed to occur? Will the transfer be delayed or fail?
It’s great that you’re aiming for 30 TPS in your MVP and factoring in future scalability. It’s also wise that you’re testing false transactions to evaluate system response, though security testing for cyberattacks will be crucial as you scale.
But this makes me wonder; how are you planning to scale beyond the 30 TPS in the first iteration?
For you to be doing beta testing first, it is showing that you want everything to come out very good and it make me glad because you do not play with your work, please tell me how are you going to pay attention to the feedback of the testers in the beta testing phase, thank you
Basically MaLink is a project that helps people keep their cryptocurrency safe.
It automatically moves funds from a wallet if it’s not used for a while or if something happens to the owner. This helps prevent lost assets and makes it easier to use cryptocurrency for regular payments. MaLink’s innovative approach and easy-to-use interface make it exciting.
My Question
Hi @Andreaxino
In case of extreme congestion where the network is overloaded, MaLink will employ a fallback mechanism. If the transfer can’t be executed immediately, it will automatically retry at regular intervals until the transaction is successfully processed, ensuring minimal delay while still optimizing for lower gas fees.
And for solving the high gas fee problem, in the future we’re planning to offer users the ability to set a maximum gas fee they’re willing to pay. If fees exceed this threshold at the scheduled time, the transfer will be temporarily paused and retried until the fees fall within the acceptable range.
After we get the feedback from testers, we will categorize, prioritize any reported issues or suggestions. This allows us to track patterns, identify critical concerns, and promptly fix any bugs or usability challenges. After that, We’ll maintain close communication with our testers throughout the process and we will loop back to testers to validate the improvements.
Hi @Okorie First thing that we need to allign is the entire transfer automation process of our system runs on smart contracts on each user’s wallet, so our system does not store any transaction data from users and everytime user setup a automation they has to sign the contract by themself.
But apart from the hacking case against the user’s wallet itself, To prevent bad things from happening in the security of our system, we do layered testing at each stage of development such as internal acceptance testing, user testing on testnet and we will conduct regural regression. Hope it asnwer your question!
Thank you for the reply, I see maintenance of feedback looping with people you will use as testers here, please tell me what incentives are you going to offer to your testers, thank you
Hello welcome to HackaTRON Season 7.i have one question. How does MaLink plan to address potential regulatory challenges associated with automated cryptocurrency transactions, particularly in regions with strict financial regulations?
Thank you for this very cool initiative, things like this can indeed help move adoption forward and provide peace of mind for existing users 
MaLink helps with lost seed phrases and automatic payments. How does it ensure safety for inactive wallet transfers, and will it integrate with other services for recurring payments?
Hey, MaLink is addressing some of the biggest concerns in the crypto world! The idea of automating payments and transfers while safeguarding assets in case of forgotten seed phrases or unforeseen events is a game-changer. I love how you’re making crypto more accessible by introducing features like recurring payments and scheduled transfers, which mirror the convenience of traditional banking.