Completed
History
It would be nice to have a breakdown of history in the dapp. Its difficult to read the explorer and know when you deposited/ withdrew from the dapp.
An Anonymous User 9 months ago
Completed
History
It would be nice to have a breakdown of history in the dapp. Its difficult to read the explorer and know when you deposited/ withdrew from the dapp.
An Anonymous User 9 months ago
Fund not received.
Today is was doing some swap on your app but after few swaps my half of the fund is not received please send me my fundβ¦
An Anonymous User 6 months ago
Fund not received.
Today is was doing some swap on your app but after few swaps my half of the fund is not received please send me my fundβ¦
An Anonymous User 6 months ago
add staked withdraw
I want / need staked token and the pool is overweighted on staked assets, but i cant withdraw staked token ( only unstaked token ). Could you add way to withdraw staked assets plz ? ty
An Anonymous User 8 days ago
add staked withdraw
I want / need staked token and the pool is overweighted on staked assets, but i cant withdraw staked token ( only unstaked token ). Could you add way to withdraw staked assets plz ? ty
An Anonymous User 8 days ago
Single Unified Activity Feed β a real-time log of all movements with extended statuses
Currently, Valantis history is essentially a set of records and transactions, but it is impossible to get a clear picture from it: what exactly happened, in what order, and where your money ultimately ended up, especially if some of the assets are used outside of Valantis itself, such as stHYPE, which is used as collateral in other protocols. The idea is to create not just a history, but a unified chronicle of the movement of each asset, where you can see absolutely everything that happened to it: you deposited, swapped, staked, unstaked, withdrew β and at the same time, you can see external events that affect the balance, such as the use of stHYPE in lending or the accrual of rewards somewhere on the side. At the same time, each operation does not have an abstract βprocessingβ status, but a clear chain of states: signed β sent to the network β confirmed on-chain β waiting for indexing β appeared in the balance, plus a human explanation of why there may be a delay and how long it usually takes, so that when the user does not see the token or funds, they do not go to the explorer thinking that everything is broken, but see directly in the interface that the asset is already theirs and the UI has simply not been updated yet. The transaction hash is available within the record itself and can be revealed if desired, but there is no need to leave the interface to check anything. As a result, users no longer have to wonder, βI swapped β where's my HYPE?β, βI staked β why hasn't it arrived?β, βSomething showed up in my rewards, but my balance hasn't changed,β because they have a live feed of events in front of them that shows the life of their capital in real time. Such a log immediately solves several real problems: it provides a normal breakdown of history without explorers, sharply reduces the number of panic cases of βfund not received,β helps to understand where exactly the assets are located, including those used as collateral, and becomes the basis for future improvements such as referrals or testnets, because this is where the user sees and controls everything that happens with their money. This is no longer a βpretty transaction history,β but a complete picture of capital movement that removes uncertainty and makes working with Valantis predictable even for those with complex positions and many parallel actions.
wafi5 About 2 months ago
Single Unified Activity Feed β a real-time log of all movements with extended statuses
Currently, Valantis history is essentially a set of records and transactions, but it is impossible to get a clear picture from it: what exactly happened, in what order, and where your money ultimately ended up, especially if some of the assets are used outside of Valantis itself, such as stHYPE, which is used as collateral in other protocols. The idea is to create not just a history, but a unified chronicle of the movement of each asset, where you can see absolutely everything that happened to it: you deposited, swapped, staked, unstaked, withdrew β and at the same time, you can see external events that affect the balance, such as the use of stHYPE in lending or the accrual of rewards somewhere on the side. At the same time, each operation does not have an abstract βprocessingβ status, but a clear chain of states: signed β sent to the network β confirmed on-chain β waiting for indexing β appeared in the balance, plus a human explanation of why there may be a delay and how long it usually takes, so that when the user does not see the token or funds, they do not go to the explorer thinking that everything is broken, but see directly in the interface that the asset is already theirs and the UI has simply not been updated yet. The transaction hash is available within the record itself and can be revealed if desired, but there is no need to leave the interface to check anything. As a result, users no longer have to wonder, βI swapped β where's my HYPE?β, βI staked β why hasn't it arrived?β, βSomething showed up in my rewards, but my balance hasn't changed,β because they have a live feed of events in front of them that shows the life of their capital in real time. Such a log immediately solves several real problems: it provides a normal breakdown of history without explorers, sharply reduces the number of panic cases of βfund not received,β helps to understand where exactly the assets are located, including those used as collateral, and becomes the basis for future improvements such as referrals or testnets, because this is where the user sees and controls everything that happens with their money. This is no longer a βpretty transaction history,β but a complete picture of capital movement that removes uncertainty and makes working with Valantis predictable even for those with complex positions and many parallel actions.
wafi5 About 2 months ago
Automate felix feusd stability pool
Here is my idea : deposit for ex 100 feusd in hype feusd stability pool, It generate yield ( who can be auto compound ) and when hype from liquidation in reward it automaticly goes to valantis hype pool ( the one selected by user if native hype StabPool or directly in associed pool ( wsthype go into wsthype valantis pool and khype go into khype pool ) ? We can even go to btc stability pool β auto compound β lend btc from liquidation and redemption to a money market for extra yield / waited to be claimed ? Idk if my idea worth it, just droping it here :)
An Anonymous User 6 months ago
Automate felix feusd stability pool
Here is my idea : deposit for ex 100 feusd in hype feusd stability pool, It generate yield ( who can be auto compound ) and when hype from liquidation in reward it automaticly goes to valantis hype pool ( the one selected by user if native hype StabPool or directly in associed pool ( wsthype go into wsthype valantis pool and khype go into khype pool ) ? We can even go to btc stability pool β auto compound β lend btc from liquidation and redemption to a money market for extra yield / waited to be claimed ? Idk if my idea worth it, just droping it here :)
An Anonymous User 6 months ago
