Capital Staking MOR projection amount is wrong
Staked on 4/FEB/2026 USDC/ERC20 with no added lock-up, with 7d cool-off period for USDC withdrawal. Projected daily emissions shown as 6 MOR/day. Claimable rewards shown (6 days later) as 8 MOR. Should be more than 30 MOR, isn’t it?
rene 2 days ago
Bugs
Capital Staking MOR projection amount is wrong
Staked on 4/FEB/2026 USDC/ERC20 with no added lock-up, with 7d cool-off period for USDC withdrawal. Projected daily emissions shown as 6 MOR/day. Claimable rewards shown (6 days later) as 8 MOR. Should be more than 30 MOR, isn’t it?
rene 2 days ago
Bugs
For Walletconnect, the dashboard requests Safe to use Ethereum
I have only a Arbitrum SAFE. And i now can’t connect to the Dashboard. I think the Walletconnect connection would need to be optimized not to attempt to change the network.
rene 23 days ago
Bugs
For Walletconnect, the dashboard requests Safe to use Ethereum
I have only a Arbitrum SAFE. And i now can’t connect to the Dashboard. I think the Walletconnect connection would need to be optimized not to attempt to change the network.
rene 23 days ago
Bugs
Planned
Can't Buy MOR
Hi there, For some reason it says I do not have any balance of USDC when trying to deposit. Thanks.
ejfinances About 1 month ago
Bugs
Planned
Can't Buy MOR
Hi there, For some reason it says I do not have any balance of USDC when trying to deposit. Thanks.
ejfinances About 1 month ago
Bugs
Slow Connect Using Safewallet
When I try to connect using safewallet it doesn’t track that it connected until after reloading the page
An Anonymous User About 1 month ago
Bugs
Slow Connect Using Safewallet
When I try to connect using safewallet it doesn’t track that it connected until after reloading the page
An Anonymous User About 1 month ago
Bugs
Completed
Staking addresses not updating
Active staking addresses are not appending/updating when new stakes are made. Simulation findings: Staking position of 20,189 MOR was not updated TX: https://basescan.org/tx/0xcf2081b27dd36fabcb4dfb41ec0ca8ce97751619010ea8224f3f051447bcc8cb Staking position of 1.1 MOR was not appended TX: https://basescan.org/tx/0x7987e5a8c597f2966786d221957e73baac66be89d56b3bd5c198d854b400f52e
Canmasu Chan About 1 month ago
Bugs
Completed
Staking addresses not updating
Active staking addresses are not appending/updating when new stakes are made. Simulation findings: Staking position of 20,189 MOR was not updated TX: https://basescan.org/tx/0xcf2081b27dd36fabcb4dfb41ec0ca8ce97751619010ea8224f3f051447bcc8cb Staking position of 1.1 MOR was not appended TX: https://basescan.org/tx/0x7987e5a8c597f2966786d221957e73baac66be89d56b3bd5c198d854b400f52e
Canmasu Chan About 1 month ago
Bugs
Completed
Statistics (up-to-date status check)
Simulation of the UX bug: 19,200 MOR was unstaked, but it still appears as staked in the UI. Claimed amount did not update even after claiming. After suspecting the statistics are not updated, we tested by staking 1 MOR twice using two wallets, but the UI did not reflect the new stakers or the increase in staked amount.
Canmasu Chan About 2 months ago
Bugs
Completed
Statistics (up-to-date status check)
Simulation of the UX bug: 19,200 MOR was unstaked, but it still appears as staked in the UI. Claimed amount did not update even after claiming. After suspecting the statistics are not updated, we tested by staking 1 MOR twice using two wallets, but the UI did not reflect the new stakers or the increase in staked amount.
Canmasu Chan About 2 months ago
Bugs
Completed
Statistics (up-to-date status check)
Simulation of the UX bug: 19,200 MOR was unstaked, but it still appears as staked in the UI. Claimed amount did not update even after claiming. After suspecting the statistics are not updated, we tested by staking 1 MOR twice using two wallets, but the UI did not reflect the new stakers or the increase in staked amount.
An Anonymous User About 2 months ago
Bugs
Completed
Statistics (up-to-date status check)
Simulation of the UX bug: 19,200 MOR was unstaked, but it still appears as staked in the UI. Claimed amount did not update even after claiming. After suspecting the statistics are not updated, we tested by staking 1 MOR twice using two wallets, but the UI did not reflect the new stakers or the increase in staked amount.
An Anonymous User About 2 months ago
Bugs
Completed
New Subnet Not Showing
I started a new subnet on Base and it shows up when I search for it and even seems to recognise that I am the owner when on the page. But it’s not showing up under the ‘my subnets’ tab. Seems to be working fine otherwise.
kyrindown About 2 months ago
Dashboard
Bugs
Completed
New Subnet Not Showing
I started a new subnet on Base and it shows up when I search for it and even seems to recognise that I am the owner when on the page. But it’s not showing up under the ‘my subnets’ tab. Seems to be working fine otherwise.
kyrindown About 2 months ago
Dashboard
Bugs
Considered
Builder and capital tab
The recommendation should disappear when users enter the Build or Capital page. Now need to swap to Left to make it disappears
Morphean 2 months ago
Builders
UI/UX Improvements
Considered
Builder and capital tab
The recommendation should disappear when users enter the Build or Capital page. Now need to swap to Left to make it disappears
Morphean 2 months ago
Builders
UI/UX Improvements
Completed
Builder dash is bugged
I can't access the builders I have MOR staked on to withdraw, nor stake additional MOR to new builders I like. Why is this a thing right now
An Anonymous User 2 months ago
Bugs
Completed
Builder dash is bugged
I can't access the builders I have MOR staked on to withdraw, nor stake additional MOR to new builders I like. Why is this a thing right now
An Anonymous User 2 months ago
Bugs
Completed
My subnet pages are crashing
both my subnet landing pages are crashing now. https://dashboard.mor.org/builders/dissentwatch-arbitrum?subnet_id=0x29d6c72e0af35f863f8c8345529ad5ad19b70b0d46225228e27c082710db4bfb&network=Arbitrum and https://dashboard.mor.org/builders/dissentwatch-base?subnet_id=0x29d6c72e0af35f863f8c8345529ad5ad19b70b0d46225228e27c082710db4bfb&network=Base - the error I get is “Error loading builder: Failed to fetch (subgraph.satsuma-prod.com)”
nima1981 2 months ago
Builders
Bugs
Completed
My subnet pages are crashing
both my subnet landing pages are crashing now. https://dashboard.mor.org/builders/dissentwatch-arbitrum?subnet_id=0x29d6c72e0af35f863f8c8345529ad5ad19b70b0d46225228e27c082710db4bfb&network=Arbitrum and https://dashboard.mor.org/builders/dissentwatch-base?subnet_id=0x29d6c72e0af35f863f8c8345529ad5ad19b70b0d46225228e27c082710db4bfb&network=Base - the error I get is “Error loading builder: Failed to fetch (subgraph.satsuma-prod.com)”
nima1981 2 months ago
Builders
Bugs
Considered
Display Default API Key
the default API key is listed below "My API Keys," which requires scrolling down when there are many keys. Placing the default API key at the top or put in button same but make it floating over API key makes it easier to see which key is in use and allows faster switching, improving usability
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Display Default API Key
the default API key is listed below "My API Keys," which requires scrolling down when there are many keys. Placing the default API key at the top or put in button same but make it floating over API key makes it easier to see which key is in use and allows faster switching, improving usability
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Use "<" Button to Switch API Instead of Pen Icon
Currently, switching between API keys requires tapping the pen (edit) icon. It would be more intuitive and faster to use a simple "<" (back) button to change or select a different API key, improving navigation and user experience.
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Use "<" Button to Switch API Instead of Pen Icon
Currently, switching between API keys requires tapping the pen (edit) icon. It would be more intuitive and faster to use a simple "<" (back) button to change or select a different API key, improving navigation and user experience.
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Adjust Chat Layout When Keyboard Pops Up
Currently, when the keyboard appears while typing, it covers the text input bar and about 40% of the messages from the bottom of the screen. It's recommended that when the keyboard pops up, the text bar and messages move up so they remain visible, and when the keyboard is dismissed, the text bar and messages return to the bottom. This improves usability and ensures smooth chatting.
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Adjust Chat Layout When Keyboard Pops Up
Currently, when the keyboard appears while typing, it covers the text input bar and about 40% of the messages from the bottom of the screen. It's recommended that when the keyboard pops up, the text bar and messages move up so they remain visible, and when the keyboard is dismissed, the text bar and messages return to the bottom. This improves usability and ensures smooth chatting.
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Shorten "API Key Ready" Popup Duration & Display API Key Name
The "API Key Ready" popup currently stays on the screen for too long. Reducing its display time to 2-3 seconds or tap the blank screen to dismiss would make the user experience smoother. Additionally, showing the API key name instead of just "API Key" would make it easier for users to quickly identify and manage their keys.
Morphean 2 months ago
UI/UX Improvements
Considered
Shorten "API Key Ready" Popup Duration & Display API Key Name
The "API Key Ready" popup currently stays on the screen for too long. Reducing its display time to 2-3 seconds or tap the blank screen to dismiss would make the user experience smoother. Additionally, showing the API key name instead of just "API Key" would make it easier for users to quickly identify and manage their keys.
Morphean 2 months ago
UI/UX Improvements
Considered
Allow Dismiss Popup by Tapping Blank Area on Mobile
On mobile devices, when the "Delete API Key" popup appears, there is currently no way to dismiss it except by selecting a cancel button. Allowing users to tap the blank area outside the popup to cancel would improve usability and make it faster and more intuitive to exit the dialog without taking action.
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Allow Dismiss Popup by Tapping Blank Area on Mobile
On mobile devices, when the "Delete API Key" popup appears, there is currently no way to dismiss it except by selecting a cancel button. Allowing users to tap the blank area outside the popup to cancel would improve usability and make it faster and more intuitive to exit the dialog without taking action.
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Add 'Jump to Latest Message' Button
When scrolling up to read older messages, there is no quick way to return to the latest message at the bottom of the chat. I have to manually scroll all the way down, which becomes difficult in long conversations. Adding a "Jump to Latest Message" or "Go to Bottom" button would make it much easier and faster to return to the newest message while browsing older chat content
Morphean 2 months ago
API Gateway App
UI/UX Improvements
Considered
Add 'Jump to Latest Message' Button
When scrolling up to read older messages, there is no quick way to return to the latest message at the bottom of the chat. I have to manually scroll all the way down, which becomes difficult in long conversations. Adding a "Jump to Latest Message" or "Go to Bottom" button would make it much easier and faster to return to the newest message while browsing older chat content
Morphean 2 months ago
API Gateway App
UI/UX Improvements