Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1392. (Read 4671936 times)

There have been several instances of people suggesting a bounty for an open source optimized AMD miner with the mining fees going to the devs.
This can provide  a long term development fund without the devs to be seen a begging. Kindly consider this option too. This seems to have much less cons than pros.

I don't entirely agree. There is no need to rush this topic, and I'm pretty sure that right now is not the time to seriously look into it, but in principle, I'd welcome if the 'emission' discussion is re-opened at a point in the not-too-distant future.

I summarized my view on the matter about a week ago in a discussion in the speculation thread as:

We (as in the core team) have indicated before that we don't do things based on the market value. Even if the value plummets overnight we will continue working. So that sort of strong-arming won't work, we'll just ignore it.

With regards to your last statement, we generally tend to agree. Every time this has come up and been bounced around as an idea we've come to the conclusion that changing the emission curve is probably a bad idea. We're stuck with it, so now we have to make it work.

XMR is the future.

can we get a serious discussion on the way to finance the development? Do we need a new thread for that?

I think the last point is the not practical/ ethical. The other two suggestions are interesting, both having it pros and cons.

I think your entering very dangerous territory by suggesting changes to core features of the coin. MEW will have significant power over the DEV team since holders can effectively collude to blackmail DEV's into following their suggestions since other wise they can dump coins and slash market prices.

MEW's role should be in helping the economy grow and business' develop not in suggesting changes to the core fundamentals of the coin. For better or worse the emission curve and block rewards are what they are and that is how they should remain.

The devs (core team) and MEW are different entities. The funding requirements mainly arise from the work that is coordinated by the devs. The monthly burn rate for developing Monero by the 7 core team members and several specialists, is significant. So far there has not been an efficient mechanism for recouping the costs already paid by the devs, and supplying the ongoing efforts. Our developers are so great that it is not fitting for them to go around begging for donations, they have rather concentrated on their excellent work and paid the outside help from their own pocket.

A great reason for MEW to even exist is that it can support the development. 50% of MEW membership fees are directed to the developers from the onset. So joining MEW automatically aids the development. More than 2000 XMR are thus received, from the founding members alone.

MEW has a voting system where the community can vote on matters related to Monero. Some members have brought it to me (as Operational Executive, it is my job to arrange the voting if 10% of the votepower so requires) to exhort the devs that Monero software should be developed to include some or all of these:
- a one-time bonus block that gives coins to the development (similar to premine that the other coins have, but "post-mine" and smaller in percentage);
- Permanent diversion of some % of the block rewards to the development;
- Slowing of emission curve, whose side effect would be that coins mined prior to the change would be considered a sort of fast mine. At this point it might be able to rally the owners of the privileged coins to donate large chuncks to the developers, since their remaining coins may likely gain in value.

It must be further underlined that:
a) the core team cannot stop the MEW members from taking whatever to be voted upon, so merely the fact that something is being discussed and/or voted in MEW, does not mean that the core team is at all behind it, and may be against it, or not even considered it.
b) if such proposal to do something with the software passes, the MEW's authority to enforce it stops there. The developers may do whatever with their coin. Since some of the core team members are also in MEW, their voting may indicate whether the resolution is likely to be implemented in the core team.

The purpose of MEW is to be a legitimate and functional way to find out what the coin owners think how things should be developed. The owners of the coin are an important peer group to the developers, eg. for a reason that the aggregate demand for ownership determines the market cap (price of the coin).

In any way you can donate to the developers directly to the donation address. Also hopefully even today, the MEW (in the mouth of David Latapie, the Members Executive) will announce that the membership is opened for everybody starting at 10 XMR entry fee.

Personally I believe excess funding leads to problems with prioritization, thus the "lean and hungry" approach will lead to better results. Concerning Monero, however, the funding situation has been ridiculous for too long already, and if the MEW is allowed to help, the problem will be put to rest even this year.

Compiling from source is not needed. apt-get install libunbound-dev

A BIG +

Restart your computer? No.

Version 1.4.22
Do I need to restart or something ?
EDIT: I did
Still don't want to install.
EDIT2: I reinstalled unbound and even rebooted. Still not working.

EDIT3: SOLVED !!

Prerequisites



Compile

What's the update on funding efforts? (This is for Devs and MEW). With the effort that was put in over the last few days and continues to be put forth, I think some people might want to give back  A thank you can only go so far.

libunbound

I ran into the same problem on Ubuntu 14.04 and solved it by installing libunbound

What's missing please ?

Pulled and rebuilt.  Block height now seems correct.

If you're building from source, that bad commit got re-applied during a merge. I've reverted it again, please pull and rebuild.

Can you increase your log with "set_log 2" so we can see why it's doing that? If you see messages like this you've pulled that reverted commit in -


2014-Sep-25 07:56:34.449024 [P2P5]coinbase transaction spend too much money (14.310913359331). Block reward is 14.307271922856(14.107271922856+0.200000000000)
2014-Sep-25 07:56:34.449060 [P2P5]Block with id: <24aa4a41e6d63dd34b1cb7a8b43f5b9315325d8ae60e7afd8d4b87374eea7ef2> has incorrect miner transaction
2014-Sep-25 07:56:34.485715 [P2P5][75.157.2.42:12237 INC]Block verification failed, dropping connection
2014-Sep-25 07:56:34.485763 [P2P5]Failed to invoke command 1002 return code -3
2014-Sep-25 07:56:34.485799 [P2P5][75.157.2.42:12237 INC]COMMAND_TIMED_SYNC invoke failed. (-3, LEVIN_ERROR_CONNECTION_DESTROYED)

I also have a node that appears to have a similar problem (but stuck at an earlier block before the last checkpoint).  I haven't tried downloading the blockchain from the OP.  I built from a new git clone.

The problem with syncing is due to not getting the latest update correctly.

From my recent update announcement:


So you can either git clone into a new destination or you can do "git reset --hard HEAD~20 ; git pull"