S
snogcel
Guest
Voted! Big congrats to the dev team for this milestone, really amazing to see the continual progression
Budget Proposal : Promotion / Reimbursement / Core Team
- Thread starter eduffield
- Start date
What a difference a year makes, huh? Let's give some colour to this thread.
Time flies...I'm pretty sure that right after Bitcoin we're the currency with the most impressing development path!What a difference a year makes, huh? Let's give some colour to this thread.
I have the feeling you are honoring our most infamous troll ^^What a difference a year makes, huh? Let's give some colour to this thread.
Last edited by a moderator:
Darkcoin wallet for Android on June 1, 2014? Where is this wallet? Afaik we still don't have a working Dash Android wallet...What a difference a year makes, huh? Let's give some colour to this thread.
https://play.google.com/store/apps/details?id=hashengineering.darkcoin.wallet&hl=enDarkcoin wallet for Android on June 1, 2014? Where is this wallet? Afaik we still don't have a working Dash Android wallet...
Oh.. Thanks, flare, i just did some digging... Yes it looks like the wallet was created during that time.. but so far, it just doesn't seem many people know about it, and currently it's not working:
https://dashtalk.org/threads/dash-wallet-for-android-release-4.4843/page-4
It doesn't mean the number of users, it just means the number of installs and reinstalls due to updates and there have been quite a few of updates... But it's not a bad number. I guess I haven't seen people talk about it much.
Yes, and that number also includes instances like myself: Install -> Try-It-Out -> No-Thx -> Uninstall ->
Me likey... Good job! That deserves a tweet:What a difference a year makes, huh? Let's give some colour to this thread.
https://twitter.com/taoofsatoshi/status/638108129184612353
yes, --litemode kills every Dash-related protocol feature and leave you with X11 litecoin + nice UI
Not using litemode anymore... Issue I'm having still persists...
Code:
mnbudget vote-many eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes
{
"overall" : "Voted successfully 0 time(s) and failed a shitload of time(s).",
"detail" : {
"MN001" : {
"result" : "failed",
"errorMessage" : "Can't find masternode by pubkey"
},
"MN002" : {
"result" : "failed",
"errorMessage" : "Can't find masternode by pubkey"
},
...Hmmm.... that's weird...
Stupid questions, I know, but:
1) are you sure you MNs are online?
2) did you change masternodeprivkeys in masternode.conf after launching MNs?
dashninja sees them all... Didn't want to trust their own output. My totally unrelated laptop wallet/client shows them in masternode list.
Nope. That'd be kinda obvious and I'd never do it. ;-)
Could there be a relationship to why I had such a bitch of a time getting them to online themselves?
Oh, and start-many does work in litemode...
The problem I had was with the nodes themselves seeming to screen themselves out. I could do a start many and MN004 would see the announcement in it's debug for everything but itself. MN117 would do the same thing... Ever damned node would see the announcement for everything but itself and continue to call itself not capable, waiting for blah blah... I finally discovered that the difference happens at the very first moment that the node checks to see if has an active announcement on the network. If it doesn't it'll never accept a new one. It's that initial check where it either works on the first try, or it'll never work. Never happened before v12.53. v12.51 didn't have that problem as far as I noticed, but I didn't have v12.51 for very long...
It can't be due to litemode usage because the announcement was successful. It's visible to everything but itself. Unless there's something undocumented/changed in regard to that...
Oh wait... Maybe... Has something significant changed in how nodes listen, or has litemode been altered recently? That might explain it... The announce is open, and doesn't get handled until the node pings or else a null address gets stuck in it, thus preventing any future announce from being loved... I wonder if this is an exploitable bug, or just a creative way to screw myself?
Last edited by a moderator:
Ok, another stupid question from me: are you sure mnprivkeys match (i.e. <mnprivkey> for mn4 in masternode.conf match "masternodeprivkey" parameter in dash.conf on remote mn4 vps)?
I just realized I've been posting this in entirely the wrong thread... But it is a voting for budget problem, I guess...
Yup. All match. I've got a screen cap I can send you if I have a gpg key (it has some sensitive data I'd rather the world not see).
I haven't altered a config file since early v11...
Last edited by a moderator:
First of all, I am very excited to officially be a part of the Dash community now In regards to OTC exchanges, within the last weeks, others have brought this idea to me...
In regards to OTC exchanges, within the last weeks, others have brought this idea to me...I will have the proposal listed soon. I look forward to having the opportunity to present a case to help solve this problem.
https://www.dashcentral.org/p/dash-adoption-tools2
I did get to posting this proposal! Not only will this proposal give Dash a friction-free OTC market, but also live phone support and live chat support for Dash newcomers (and crypto newcomers), an API that will help Dash app developers build a revenue base to support their development, and if we don't use all of the budget, we'll use it to continue developing to integrate into other Dash applications I greatly look forward to the opportunity to serve the Dash community and help the ecosystem grow!
I did get to posting this proposal! Not only will this proposal give Dash a friction-free OTC market, but also live phone support and live chat support for Dash newcomers (and crypto newcomers), an API that will help Dash app developers build a revenue base to support their development, and if we don't use all of the budget, we'll use it to continue developing to integrate into other Dash applications
I greatly look forward to the opportunity to serve the Dash community and help the ecosystem grow!
I think the operative term was "working."
This wallet crashes every time I try to IX, and will never load again until it is uninstalled/re-installed, which, of course, deletes the wallet... And is the only reason why it works again.
If I shut off all networking, it'll stop instacrashing post IX attempt. But that's kinda useless. As soon as networking is enabled, crash. Using IX in this wallet is a great way to be forced to delete your coins.
This particular error has been reported by some, but I haven't been able to reproduce it in my testing. For me on several devices the Dash Wallet app doesn't crash when sending IX.
There is an unreleased update that has other fixes and this problem may have been fixed as well: https://github.com/HashEngineering/dash-wallet/releases/tag/v4.65.12A
In the mean time the solution is to turn off Networking or Wifi, then reset the blockchain, then turn back on Networking or Wifi. This will clear the stuck transaction that is crashing the app everytime it starts.
