I really like having the core fundamentals like block time etc somewhere within the wallet too.
Indeed, the question is just, do we want this information to go into the "Network Overview" constantly visible in the header?  Or do we want to put it as secondary information in the not constantly visible overview page. So this is about priority. My vote is for secondary information but easily findable. Well, it's not an either or. We can use both. I like that the network box in the header informs us about things that are changing on a per minute basis. Secondary information should be everything else. |
|
|
|
I really like having the core fundamentals like block time etc somewhere within the wallet too.
Indeed, the question is just, do we want this information to go into the "Network Overview" constantly visible in the header? Or do we want to put it as secondary information in the not constantly visible overview page. So this is about priority. |
|
|
|
If it was perfect, it wouldn't need improvement  Give me a few mins to bounce a few ideas around like a squash ball in my skull. Now you are talking! |
|
|
|
"Welcome to SpreadCoin, the project that is building a network where any application or service can be run in a decentralised manner."
I like it, but still.... This is concentrating too much on the future, and not so much on what we already have achieved. I understand and respect your opinion on this but I also think a balance needs to be struck. In project management the short, mid and long term goals of a project should be advertised and agreed by the project sponsors who in this case are the open source community at large. Focussing on what we are doing right now is missing a chance to gain direction and support from the wider community in the future. I can't think of an argument for not mentioning what is on the roadmap in the wallet. I agree with that. I was just saying, your wording was focusing completely on the future. What I want is some balance that also mentions the present. If you could extend the wording ... Its a tricky balance! I think I need another coffee! "Welcome to SpreadCoin, the project that is building a network where any application or service can be run in a decentralised manner." See, I could never come up with such a line, that's why I need your help with this. But I want you to make it MORE perfect.  |
|
|
|
 ..... the emissions curve...brb ......... Plus, main features? That's an interesting point. I know of no wallet that informs the user about its specifications WITHIN the wallet. So you are always forced to go visit the official site / blockexplorer to even know such things as blocktime, current blockreward, port, etc... So, we could very well reuse part of the overview screen for such information. But keep in mind that we already have a section of the header reserved for "network information": so I am not sure |
|
|
|
...
The QT splashscreen looks like this already:
...
yes, and it looks great. So why not keep the theme in the wallet when its open? Yes, we can start the introductory text with "Decentralize everything" as title... but what follows then? Can we get protocol versions in there, keep them updated so people know which is the latest? Yes, that's what the alert system is here for. Once we start using it, the main devs can trigger alert messages for all kinds of things. |
|
|
|
"Welcome to SpreadCoin, the project that is building a network where any application or service can be run in a decentralised manner."
I like it, but still.... This is concentrating too much on the future, and not so much on what we already have achieved. I understand and respect your opinion on this but I also think a balance needs to be struck. In project management the short, mid and long term goals of a project should be advertised and agreed by the project sponsors who in this case are the open source community at large. Focussing on what we are doing right now is missing a chance to gain direction and support from the wider community in the future. I can't think of an argument for not mentioning what is on the roadmap in the wallet. I agree with that. I was just saying, your wording was focusing completely on the future. What I want is some balance that also mentions the present. If you could extend the wording ... |
|
|
|
...
The QT splashscreen looks like this already:
...
yes, and it looks great. So why not keep the theme in the wallet when its open? Yes, we can start the introductory text with "Decentralize everything" as title... but what follows then? |
|
|
|
"Welcome to SpreadCoin, the project that is building a network where any application or service can be run in a decentralised manner."
I like it, but still.... This is concentrating too much on the future, and not so much on what we already have achieved. Keep in mind, we can change the text with every following wallet version, so we should stay rather specific on the current state of the wallet. |
|
|
|
Nothing there about servicenodes.
maybe make one of the big boxes, Service Nodes, coming soon
Hm, not a big fan of this idea. We should restrict it to what we have, not what we like to have. We can add such additional boxes once the first testnet version is out. |
|
|
|
About the introductory text, I can do it so that different texts appear depending on if the user starts the wallet for the first time or some other event has occured.
Decentralize Everything As the QT loading screen The QT splashscreen looks like this already:  |
|
|
|
|
About the introductory text, I can do it so that different texts appear depending on if the user starts the wallet for the first time or some other event has occured.
The future goal will also be to post an alert message in this field, (rather then at the bottom at the sync progress bar) when the alert system is used by the main devs.
And maybe even inform the user that he hasn't done a backup in over X days...
you get the idea.
|
|
|
|
Guys, I am nearly finished with the wallet, I am doing the last tests to finish the vanity gen. But I am going to need some help with the overview screen. This is the general structure I want it to have:  Now I need you guys to help me with the "wording" of all the elements. |
|
|
|
remove return vp;
and replace it with ptrp = &itemp->ai_left;
And it doesn't even matter if I replace it with ptrp = &itemp->ai_right; It works either way. Thanks again. |
|
|
|
 It works if I do this: static vg_prefix_t *vg_prefix_avl_insert(avl_root_t *rootp, vg_prefix_t *vpnew)
{
vg_prefix_t *vp;
avl_item_t *itemp = NULL;
avl_item_t **ptrp = &rootp->ar_root;
while (*ptrp) {
itemp = *ptrp;
vp = avl_item_entry(itemp, vg_prefix_t, vp_item);
if (BN_cmp(vp->vp_low, vpnew->vp_high) > 0) {
ptrp = &itemp->ai_left;
} else {
if (BN_cmp(vp->vp_high, vpnew->vp_low) < 0) {
ptrp = &itemp->ai_right;
} else
ptrp = &itemp->ai_left;
//return vp;
}
}
vpnew->vp_item.ai_up = itemp;
itemp = &vpnew->vp_item;
*ptrp = itemp;
avl_insert_fix(rootp, itemp);
return NULL;
} remove return vp; and replace it with ptrp = &itemp->ai_left; Thanks again for the hint, TheRealSteve! You really are The Real Steve!
|
|
|
|
There's an edge condition where the two are considered equal, the 'else [...] return vp;' part. You want to eliminate that. Should be as simple as changing one of the comparisons from '>' or '<' to '>=' or '<=' respectively.
Not sure if that breaks anything, but give it a shot.
Thanks, I tried that, removing the part and changing either to >= or <=, but it doesn't work. It looks like the program isn't even starting the search cycle anymore. |
|
|
|
Try with -r command. It is working for me. Another example: what if I want to feed those patterns into vanitygen: 1super 1superd 1superdu 1superdup 1superdupe 1superduper and I want it to print out the privkey/pubkey pair whenever one of those matches is found. What method can I use to achieve that and REALLY have vanitygen print out all intermediate key pairs, without ignoring my wishes. PS: I know that I can achieve that by starting 6 different vanitygen processes. But I do require that this happens withing one vanitygen process. I tried with these but I vanitygen is only finding for 5 keywords not 6 but it is better than nothing.  Thanks, so it requires regex. What if I don't want to use regex, but rather adjust vanitygen so that it doesn't ignore overlaps? |
|
|
|
Another example: what if I want to feed those patterns into vanitygen: 1super 1superd 1superdu 1superdup 1superdupe 1superduper and I want it to print out the privkey/pubkey pair whenever one of those matches is found. What method can I use to achieve that and REALLY have vanitygen print out all intermediate key pairs, without ignoring my wishes. PS: I know that I can achieve that by starting 6 different vanitygen processes. But I do require that this happens withing one vanitygen process. |
|
|
|
Could you please give an example. I am not understanding correctly. It would be great if you give an example for the problem and for what you are trying to achieve.
Very well. The way vanitygen works now, is that it allows us to search for multiple patterns simultaneously (by starting vanitygen once and passing parameters once). And it will keep on working to find matches for all those patterns, printing out the resulting privkey/pubkey when one is found. Very good. Suppose I now want to start vanitygen looking for those patterns: 1something, 1super, 1superduper Now, depending on what pattern is listed first, vanitygen will complain that either Prefix '1superduper' ignored, overlaps '1super' or if the list is ordered differently, like that: 1something, 1superduper, 1super: Prefix '1super' ignored, overlaps '1superduper' I would like vanitygen to NOT do that, but instead work with all patterns listed, and printing out resulting keys when a match is found. This means that I expect vanitygen to find a match for 1super in short time (and print out the resulting keys), and continue looking for a match of 1superduper. Vanitygen doesn't allow me to do that. Can someone who understands the code give me a hint what functions I need to disable/adjust so that overlapping patterns don't get removed/ignored? Thanks. |
|
|
|
You can't take a result '1Super', and then feed that back into vanitygen to get '1SuperDuper' at a lower cost.
When did I ever say that I want to "save time" or achieve "lower cost"? I don't want to "feedback" anything. As I stated, I just desire that vanity gen doesn't automatically get rid of patterns that overlap,but instead it should continue working with them as if they were unique searches. Right now, vanity gen stops the processing of overlapping patterns, I would like that it continues the processing anyway. |
|
|
|
|
Show Posts
