Anyway all I was really trying to say was that for coins like DRK and MRO, ninja launch, small instamine, or whatever you want to call it will do little to scare most people off when they see how much the coin has to offer in contrast to the other 99%.
The problem is, that does invite a clone that has everything to offer that the original does, minus the premine. The main reason MRO exists and is doing so well is the large ninja instamine by the predecessor. You could be right that a small instamine isn't that a big deal though. 80% is a bit much.
|
|
|
Do anybody use a linux os for his wallets successfully? What's the os name and version? Do I have to compile the wallet sw on my own?
I use ubuntu 13.10 and compile myself. Compilation is very easy. git clone blah blah sudo apt-get install build-essential sudo apt-get install boost-all-dev cd bytecoin make What's your compiled wallet version? The one right after the tx extra fix. I haven't updated since then.
|
|
|
0.000900 / MRO / 0.5 btc
Added. I kept your old order. Let me know if you want it removed.
|
|
|
I have my coins again, so a brief aggregation now. I'm working with Ubuntu Linux 12.04, installed as Virtual Machines on top a VirtualBox environment. My Ubuntu installation is for wallets only, standard installation, some with VPN prepared. One week before all worked as expected, I created a lot of wallets for exchanging BCN. But beginning from yesterday I got this message on start of simplewallet and every refresh: Error: refresh failed: transaction extra parse error. Blocks received: 6321 A dozen of wallets failed, residing on three different VMs, residing on three different hardware. Also with the newest wallet version (0.8.5.306) it failed to refresh. Surprisingly newly created wallets are working, but not the old ones. I have now installed a wallet into windows 7 (version 0.8.6.56), syncronized the blockchain, created a new wallet successfully. Then I transfered my Ubuntu wallets into windows, renamed the large wallet-file, and voila, the refresh finished without any error, showing the correct balance. I have downloaded the newest binaries for windows or linux. I wonder that the version differs significantly between the two os. The linux version perhaps is not uptodate. I could compile it on my own, if I would find a hint about it to be necessary. But as a marketing guy already said about BCN: If the usability does not increase, this coin is useless. What I also wonder about: as a coin with preference to anonymization and security there should be a large community of linux users here. Do anybody use a linux os for his wallets successfully? What's the os name and version? Do I have to compile the wallet sw on my own? I use ubuntu 13.10 and compile myself. Compilation is very easy. git clone blah blah sudo apt-get install build-essential sudo apt-get install boost-all-dev cd bytecoin make
|
|
|
Someone let me know when another clone of this coin comes out. I want to get in on it right at launch.
You can't just keep cloning shitcoins and expect them to go anywhere. This coin had a compelling purpose since BCN was ninja premined for 80%. There is no such advantage that another clone would have over this one. Stay here and mine. The reward curve is mostly flat now. In six months the current difficulty may look extremely low. EDIT: In fact in six days the current difficulty may look extremely low.
|
|
|
It could and was argued that DRK gave early miners an unfair advantage, ninja launch etc. but in the end had no effect on its future.
1. How do you know the effect? What would have happened without the launch issues. 2. The future is still being written. CryptoNote has the potential to render DRK obsolete anyway. We'll see.
|
|
|
The emission curve vote was rejected by a bit over 60% earlier when there were fewer people involved so it will fail by even larger margin now. The reason is simple: the OTC exchange has a pretty sizable volume and the amount of hardware dedicated to this coin is getting larger. Part of how people price the currency unit or decide how much hardware to dedicate to mining it is to compare the amounts they gain to the eventual maximum supply. Amount relative to current supply also matters, certainly even more, but it's undeniable that the former is involved. People have been making these decisions based on the current curve.
In order to fairly implement an emission curve change, we need to retroactively adjust everything mined up to that point. If we don't, it's an instamine where the early adopters changed the rules in the middle of the game to benefit themselves. But on the other hand, a retroactive adjustment means miners/buyers/sellers all made decisions on false information. This is why there were a lot of complaints about "taking my coins away" earlier.
So the most agreeable thing to do is to leave the curve as it is. About 8 years from now, we'll have a problem where the block reward is fairly small and miner don't mine for nothing. The solution to that is to implement a minimum subsidy. This would cause a sub-1% inflation that decreases over time and keeps miners happy to ensure network security. tacotime will probably implement this in hard fork in the near future.
Thanks eizh for explaining, I missed this news that this was what was decided. Well the pool on the forum failed to get a majority but there is zero protection against ballot stuffing with newbie accounts so who knows what that really means. If we had a voting mechanism in the coin itself we could use that to get a more reliable vote, but we don't. I do agree there is a widespread objection about either taking coins away or giving early miners an unfair advantage, so it likely best to just leave it the way it is and implement a longer term fix to the somewhat overly fast curve over the scale of years/decades as eizh mentioned. Can this be resolved with something like slowly moving the block target to 2 or 2.5 or x minutes over the course of a few years? At this point, it would probably be much more favorable to come up with long-term, barely visible solutions rather than shocks. I don't know the protocol though -- you guys do so I'm probably just making it harder than it needs to be. It sounds like you're in favor of somehting like this too. I get what you're saying about ballot stuffing, lots of new accounts in this thread. I understand the need to have a correction, but is there any way to cause it to appear as a crawl rather than a shock? I'd rather lose a miniscule amount every day rather than rip out a tooth all at once . . if possible. Yeah anything that's done will probably be slow like that. The leading idea of just making the reward bound at some minimum or perhaps slow to some minimum won't even kick in for years.
|
|
|
WTS 0.02 / 1000 MRO / 20BTC
Hey you never know, right? Added
|
|
|
The emission curve vote was rejected by a bit over 60% earlier when there were fewer people involved so it will fail by even larger margin now. The reason is simple: the OTC exchange has a pretty sizable volume and the amount of hardware dedicated to this coin is getting larger. Part of how people price the currency unit or decide how much hardware to dedicate to mining it is to compare the amounts they gain to the eventual maximum supply. Amount relative to current supply also matters, certainly even more, but it's undeniable that the former is involved. People have been making these decisions based on the current curve.
In order to fairly implement an emission curve change, we need to retroactively adjust everything mined up to that point. If we don't, it's an instamine where the early adopters changed the rules in the middle of the game to benefit themselves. But on the other hand, a retroactive adjustment means miners/buyers/sellers all made decisions on false information. This is why there were a lot of complaints about "taking my coins away" earlier.
So the most agreeable thing to do is to leave the curve as it is. About 8 years from now, we'll have a problem where the block reward is fairly small and miner don't mine for nothing. The solution to that is to implement a minimum subsidy. This would cause a sub-1% inflation that decreases over time and keeps miners happy to ensure network security. tacotime will probably implement this in hard fork in the near future.
Thanks eizh for explaining, I missed this news that this was what was decided. Well the pool on the forum failed to get a majority but there is zero protection against ballot stuffing with newbie accounts so who knows what that really means. If we had a voting mechanism in the coin itself we could use that to get a more reliable vote, but we don't. I do agree there is a widespread objection about either taking coins away or giving early miners an unfair advantage, so it likely best to just leave it the way it is and implement a longer term fix to the somewhat overly fast curve over the scale of years/decades as eizh mentioned.
|
|
|
Can we have the daemon auto-save the blockchain? Maybe every 30 minutes or so.
It does that. I don't know what triggers it though. My windows computer automatically restarted itself last night for a windows update. The blockchain went back to when I manually saved it 10 hours ago so it doesn't seem to be saving. It only saves when you type "save" or "exit". Well I see it claiming to do so in the daemon output, but I'm on linux. Maybe that makes a difference, or maybe its not really saving it.
|
|
|
Can we have the daemon auto-save the blockchain? Maybe every 30 minutes or so.
It does that. I don't know what triggers it though.
|
|
|
At the current MRO price (0.001 BTC) and BTC price ($430), we have $2,463 donated. The goal is $2,500. The difference is negligible. So should we sell the MRO now at 0.001 BTC?
Edit: I will donate 0.1 BTC to cover the difference.
It has been trading at 0.001 but we can't guarantee we could exchange the bounty fund for that. Maybe we could. Whoever is in touch with the developer should ask him what he wants done with the fund. I agree there should be enough value there one way or another to get this done.
|
|
|
New buy order
0.001000 / 1750 MRO 1.75 / contact OP
Filled. All updates made
|
|
|
bitmonero wallet v0.8.6.295() password: ************* Opened wallet: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Starting refresh... Error: refresh failed: daemon is busy. Please try later. Blocks received: 0
Can't refresh (tried multiple time), bitmonero compiled from source and the daemon is fully synced. This is not working since few days, I updated source but still not working. The daemon can mine however. Any idea ? Edit : using libboost 1.53 Try typing "save" in the daemon window It worked thanks ! But that's strange since I did multiple exit and relaunch witch would have saved the blockchain. Any way ... good to know. Some kind of race condition in the code. Sometimes it comes up with broken RPC, sometimes it works fine. Doing "save" seems to resolve it.
|
|
|
bitmonero wallet v0.8.6.295() password: ************* Opened wallet: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Starting refresh... Error: refresh failed: daemon is busy. Please try later. Blocks received: 0
Can't refresh (tried multiple time), bitmonero compiled from source and the daemon is fully synced. This is not working since few days, I updated source but still not working. The daemon can mine however. Any idea ? Edit : using libboost 1.53 Try typing "save" in the daemon window
|
|
|
New buy order
0.001000 / 1750 MRO 1.75 / contact OP
|
|
|
I have a few more coupons (both S1 and S2) and I will order miners for you using the coupons if you pay me advance. No charge, tips welcome.
sry maybe a noob question here but whats the point of going through with your coupons? isnt it much simpler to just order via their website and pay them directly? The coupons give a discount -0.05 btc for S1 -$400 for S2
|
|
|
Willing to remove the QR code or change the adress to an adress provided by smooth for his work in this thread Awesome work. Leave the code. I'll copy the image to the first post.
|
|
|
I have a few more coupons (both S1 and S2) and I will order miners for you using the coupons if you pay me advance. No charge, tips welcome.
|
|
|
Guys! Don't trade with LethalStriker. He got my BCN and disappeared!
He wrote me! Proof? Sent him 10mil in the morning. Still no btc from him, though he said that received the money. Better to use escrow
|
|
|
|