We take suggestions from our community seriously.
Here is a compilation of all the relevant suggestions from the Spacemesh Discord #suggestions channel, since May of 2022, with responses from the team.
Suggestion (from ticktockbent):
a pinned topic or even a persistent channel listing known scams and fraudulent “space mesh token sales” sites etc so people can look up suspected scams/sites
Response: This is a great idea that we will be implementing.
Suggestion (from Turbo):
Hi there, I’d like to suggest a ‘Testing’ channel for the discord server. It may be something that you prefer to keep internal and that’s fine, but I’m using Sikulix to send a few test transactions on the network and maybe would like to share testing experiences etc.
Response: We feel like this function is already covered by “network_discussion”.
Suggestion (from saki2fifty): I haven’t been around for the past 6+, and have since forgotten what is used for what. I’m old, smart and can figure it out but would be nice if we had a basic app chart for those who are new, or just old and forgetful like me. For instance: For those wanting to use their home Windows pc: [Required App] purpose: xxxx [Required App] purpose: xxxx [Alternative app] purpose: xxxx For those wanting to using a ‘Nix based server (cli): [Required App] purpose: xxxx [Required App] purpose: xxxx [Alternative app] purpose: xxxx For those wanting to create PoST files (GPU/cli): [etc] [etc] There are 90 repositories, so on first glance it’s overwhelming… even the main SM site. I’m sure the next reply will be… “We already have that… [here}”. I’m still going through it all and re-educating myself…
Response: We are in the process of creating a centralized, streamlined documentation, and instructions like these will be a part of it.
Suggestion (from cipoint): The rewards are ordered by ascending and descending time in this two views:https://explorer.spacemesh.io/accounts/stest1qqqqqqzr33ce8dvu466ev438cwmkh5pezugk26su676dr/rewardshttps://explorer.spacemesh.io/smeshers/stest1qqqqqqz6597lq4jya82655eqpf5tsgcrkgjrhkqaax475/rewards The should either be ordered identically or -better- offer an option for sorting.
Response: This will be implemented in the UI.
Suggestion (from jinhuanming & wnft): please support multiple HDDs at genesis.
Response: This will not be possible at genesis, but may be implemented later.
Suggestion (from andreastom84): i have a suggestion if someone is using multiple harddrives in one PC or wants to allocate space on different drives, maybe he got an external HDD also, then it would be great to be able to add another PoS file. Lets say, i got 300gb free on C: and 2tb on D: and first i allocate 250gb of c: and then make another PoS file for D:
Response: This is not supported for now. You can do that by linking to them from one location
Suggestion (from wnft): support for 24 mnemonic words
Response: This will be implemented in the future.
Suggestion (from monivong): I’ve seen this in the transaction log before but a breakdown of daily, monthly and annually earning from smeshing would be helpful to smeshers.
Response: This has been implemented.
Suggestion (from monivong): I think we should be able to select to see outbound/inbound transactions in the wallet tab again.
Response: We will be implementing this in the future.
Suggestion (from yast123): Will be cool enlarged counter with arrow clamp, now you have to do a lot of extra clicks [for PoST]
Response: This has been implemented.
Suggestion (from andreastom84): Hi there! I have a GUI suggestion. It would be nice if we could see the estimated time depending on the GPU and hardware used it will take to fill up the space in realtime. i.e. you type in 500gb and smapp shows about 20 hours or so. you change that variable and the estimation changes
Response: It’s hard to provide exact numbers, because the benchmark that we run is quick & fast so it may not present the most up-to-date numbers.
Suggestion (from snakelips): I suggest if the node is having trouble staying running, have it write some kind of output reasoning to the log file. So far, after fighting to keep my nodes running, the log file is empty.
Response: If your log file is empty, it means that the node itself has crashed on startup. This is probably due to missing libs.
Suggestion (from snakelips): Show the status of each required piece. I don’t know all the pieces, but you said two - blockchain sycn and connection to other nodes. Maybe list those, along with other critcal pieces, a red/yellow/green light next to them, along with a restart button where applicable, and some note of what might be the problem.
Response: This has been implemented.
Suggestion (from snakelips): Suggest there be some kind of visual indication (red/yellow/green light) showing status of the node in the program when minimized in the tray, so you don’t have to restore it to full size.
Response: This will be implemented in the future.
Suggestion (from ticktockbent): Change the initial 0-119 sync display on node startup to say something like “Syncing Genesis Data (This may take a while)”
Response: This has been implemented.
Suggestion (from Stizerg): Can you add an indicator (green/orange/red) to the smashing tab, to make it similar to network tab. Green = smeshing alright, Orange = creating file, Red = something is wrong
Response: This is currently being implemented.
Suggestion (from cipoint): Can we have MiB/s either instead of hashes/sec or alongside? [when selecting GPUs in PoST init]
Response: This will be implemented in the future.
Suggestion (from yorickdowne): The benchmark feels slightly silly. It benchmarks the system, then suggests I create 7.8 TiB of data – I don’t have 7.8 TiB at all, never mind free. It’s a 4TB SSD with 1.7 TiB free. So, having the “recommended MAX space” setting adjust itself to actually available free space, keeping in mind it should leave some for other things, sounds like a good idea.
Response: We are in the process of changing that screen, and it’s likely this will be implemented.
Suggestion (from yorickdowne): Looking at the GUI, the use of both PoS and POST is a bit confusing. Maybe stick with just POST or PoST? As in “Started creating PoST data” instead of “Started creating PoS data”, to match “PAUSE POST DATA GENERATION”
Response: This will be implemented in the future.
Suggestion (from cipoint): Smeshers are repeatedly irritated by their initialized nodes not smeshing for more than one epoch. I suggest a more talkative GUI, which for example tells the smesher that: he/she finalized the initalization (this is already implemented) ;his node will be asked to deliver a proof at date XX and time YY OR the node has already successfully delivered the proof at date XX and time YY; incoming rewards are expected to start at date XX and time YY. I think this will strongly reduce the frustration and uncertainty on the user side. This won’t change the fact, that some smeshers will have to wait for more than 2 epochs for the first rewards. But I foresee, that in the mainnet, when an epoch is 14 days and the phase shift is 7 days, the discord channel will be flooded with questions like “where are my rewards?” And we don’t want to lose smeshers just because of misunderstanding.
Response: We are in the process of improving node status, so improvements along these lines will be coming in the future.
Suggestion (from stizerg): Please prevent an automatic POST files deletion without user’s confirmation.
Response: Currently it can happen only when node finds that something is wrong with POST files, i.e. thenode is configured to run with a different state than the one found on the disk. But we will be implementing measures to make sure these aren’t deleted prematurely.
Suggestion (from stizerg): Could you implement following algorithm : 1. Smapp checking for available POST files, counting existing (already created) POST units. 2. IF “smeshing-opts-numunits” in current configuration is more then found POST units, continue creating POST files. (current behavior). 3. IF “smeshing-opts-numunits” in current configuration is less then found POST units, adjust Smapp configuration according to the number of found units. 4. Repeat step 1 after 3600 seconds.
Response: That’s risky behavior, because it could easily end up with “growing post”, or initializing post while it should be proving it etc. So on those grounds, we will not be implementing this suggestion.
Suggestion (from Henry Mumbles): A legend for what the different colours mean on the transactions. blue, orange, green, grey, what do they mean
Response: We feel that such a legend will add unnecessary noise/mess and content overload, and that all this information is already available in the transaction log. As such, we will probably not be implementing this suggestion.
Suggestion (from saki2fifty): When viewing “All Transactions” in smapp, have the option to filter by date
Response: This will be implemented in the future.
Suggestion (from ticktockbent): On [the progress indicator] of the smesher interface when generating the initialization data, include a calculated rough estimate of the initialization speed and estimated time of completion. For example: `11.92 GiB / 800 GiB, 1.49% - ~22 GiB/hr - ~36 hours left`
Response: This will be implemented in the future.
Suggestion (from Amadis11#8495): PoST data should be firstly initialized and then it could be made bigger but smeshing would work in background on first data. Then after adding second batch on smeshing would work on 1st and 2nd and etc. E.g. when I will initialize 32GB of post data in 2GB files then I should start smesh with these. After this there should be an option to simply add another 32GB of data and another and another , but smeshing will work firstly on 32Gb, then 64GB, then 96GB etc. We should have multiple drive locations available also.
Response: This will not be present at genesis, but something very similar will be implemented in the future.
Thank you so much for sharing your valuable insights and feedback! We are in the process of turning the accepted suggestions (that have not already been implemented) into issues on our main github repo, as well as our smapp repo.
Join our newsletter to stay up to date on features and releases
