So I need to provide my address now?
Yes you have 2% of the bounty coming to you.
Need MRO, BCN, and BTC addresses.
The remaining funds in the XMR (MRO), BCN, and BTC pool bounty wallets have been distributed to archit.
Topic: Bounty for open source ByteCoin/Monero pool (Read 14672 times)
Yes you have 2% of the bounty coming to you.
Need MRO, BCN, and BTC addresses.
The remaining funds in the XMR (MRO), BCN, and BTC pool bounty wallets have been distributed to archit.
Is this the right place to get help with these pools? npm update fails with
npm ERR! 404 'cryptonote-util' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.
and
npm ERR! Error: version not found: 0.0.9 : multi-hashing/0.0.9
npm ERR! at RegClient. (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:259:14)
npm ERR! at Request.init.self.callback (/usr/local/lib/node_modules/npm/node_modules/request/main.js:120:22)
npm ERR! at Request.EventEmitter.emit (events.js:99:17)
npm ERR! at Request. (/usr/local/lib/node_modules/npm/node_modules/request/main.js:648:16)
npm ERR! at Request.EventEmitter.emit (events.js:126:20)
npm ERR! at IncomingMessage.Request.start.self.req.self.httpModule.request.buffer (/usr/local/lib/node_modules/npm/node_modules/request/main.js:610:14)
npm ERR! at IncomingMessage.EventEmitter.emit (events.js:126:20)
npm ERR! at IncomingMessage._emitEnd (http.js:366:10)
npm ERR! at HTTPParser.parserOnMessageComplete [as onMessageComplete] (http.js:149:23)
npm ERR! at CleartextStream.socketOnData (http.js:1367:20)
npm ERR! If you need help, you may report this log at:
npm ERR!
npm ERR! or email it to:
npm ERR! <[email protected]>
wtf is npm, btw? there a way i can do what it's trying to manually?
npm ERR! 404 'cryptonote-util' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.
and
npm ERR! Error: version not found: 0.0.9 : multi-hashing/0.0.9
npm ERR! at RegClient.
npm ERR! at Request.init.self.callback (/usr/local/lib/node_modules/npm/node_modules/request/main.js:120:22)
npm ERR! at Request.EventEmitter.emit (events.js:99:17)
npm ERR! at Request.
npm ERR! at Request.EventEmitter.emit (events.js:126:20)
npm ERR! at IncomingMessage.Request.start.self.req.self.httpModule.request.buffer (/usr/local/lib/node_modules/npm/node_modules/request/main.js:610:14)
npm ERR! at IncomingMessage.EventEmitter.emit (events.js:126:20)
npm ERR! at IncomingMessage._emitEnd (http.js:366:10)
npm ERR! at HTTPParser.parserOnMessageComplete [as onMessageComplete] (http.js:149:23)
npm ERR! at CleartextStream.socketOnData (http.js:1367:20)
npm ERR! If you need help, you may report this log at:
npm ERR!
npm ERR! or email it to:
npm ERR! <[email protected]>
wtf is npm, btw? there a way i can do what it's trying to manually?
May be you can put the link to the pool source code in the OP ?
So I need to provide my address now?
Yes you have 2% of the bounty coming to you.
Need MRO, BCN, and BTC addresses.
[/quote
I'll message them soonSo I need to provide my address now?
Yes you have 2% of the bounty coming to you.
Need MRO, BCN, and BTC addresses.
So I need to provide my address now?
This argument does not apply where Monero is the donor chain because it is illogical to mine the merged mining chain (Fantomcoin) only
It is illogical to mine any merge mined coin on its own. That's exactly the point.
Quote
There were no arguments against Monero being a donor chain.
The argument is that it ultimately turns into an arms race where everyone has to mine every merged mine coin in order to remain competitive. This has both practical and ethical negatives.
The practical is that carries greater costs for the miner of running and maintaining more nodes, holding or selling more coins, etc., with ultimately the same value return (since difficulties adjust to approach break even on total value returned).
The ethical is that miners should be able to choose which coin or coins to support without putting themselves at a structural competitive disadvantage. This is accomplished with individual mining where a coin recruits its own miners based on the merits of the coin itself.
There are other, more complex and subtle issues I choose not to address right now because they aren't needed to explain why merged mining isn't wanted for Monero, never has been, and likely never will be.
Both of these issues are exactly the same whether the mining is merged with BCN or FCN and whether the mining is donor or daughter.
But as I said, there is certainly no technical reason why the pool software can't support it, though in addition to questioning whether it is a good investment, I would also question whether this should really be a priority for pool software that still isn't reliable, etc.
How would support for merged mining with Fantomcoin be removed? 
Most of the reasons for opposing merged mining with Bytecoin was to not be associated with it.
The other reasons were similar to this one:
This argument does not apply where Monero is the donor chain because it is illogical to mine the merged mining chain (Fantomcoin) only, so the effect on donor chain difficulty is non-existent. This argument only applies when Monero is the merged mining chain.
There were no arguments against Monero being a donor chain.
Most of the reasons for opposing merged mining with Bytecoin was to not be associated with it.
The other reasons were similar to this one:
Let me explain this with a simple example (we consider the blocktime is the same for each chain):
Let's say there is 20 peoples mining with the same hardware
They are mining for the duration of 40 blocks.
So 40 blocks of Bytecoin will be produced (noted : BytecoinB)
So 40 blocks of Monero will be produced (noted : MoneroB)
- Without Merged Mining (current situation):
10 people are mining Bytecoin
10 people are mining Monero
On average, for 40 block in the blockchain, each user will get 4 blocks of the chain he mine (40/10).
So :
10 people get 4 BytecoinB
10 people get 4 MoneroB
- With Merged Mining :
20 people are merged mining Bytecoin and Monero
On average, for 40 block in the blockchain, each user will get 2 blocks of each chain (40/20).
So :
20 people get 2 BytecoinB
20 people get 2 MoneroB
- Conlusion :
Without Merged mining, you can chose to have either 4 BytecoinB or 4 MoneroB.
With Merged mining, you will have 2 BytecoinB and 2 MoneroB.
- Side note :
With this example it's easy to understand why (if you are a rational economic agent) you don't have the choice to not do merged mining if its available (you will just lose 2 BytecoinB).
So if you think Bytecoin was ninja mined and you don't want to validate that with your hash power, you better not want merged mining to be implemented in Monero.
SlyWax.
Let's say there is 20 peoples mining with the same hardware
They are mining for the duration of 40 blocks.
So 40 blocks of Bytecoin will be produced (noted : BytecoinB)
So 40 blocks of Monero will be produced (noted : MoneroB)
- Without Merged Mining (current situation):
10 people are mining Bytecoin
10 people are mining Monero
On average, for 40 block in the blockchain, each user will get 4 blocks of the chain he mine (40/10).
So :
10 people get 4 BytecoinB
10 people get 4 MoneroB
- With Merged Mining :
20 people are merged mining Bytecoin and Monero
On average, for 40 block in the blockchain, each user will get 2 blocks of each chain (40/20).
So :
20 people get 2 BytecoinB
20 people get 2 MoneroB
- Conlusion :
Without Merged mining, you can chose to have either 4 BytecoinB or 4 MoneroB.
With Merged mining, you will have 2 BytecoinB and 2 MoneroB.
- Side note :
With this example it's easy to understand why (if you are a rational economic agent) you don't have the choice to not do merged mining if its available (you will just lose 2 BytecoinB).
So if you think Bytecoin was ninja mined and you don't want to validate that with your hash power, you better not want merged mining to be implemented in Monero.
SlyWax.
This argument does not apply where Monero is the donor chain because it is illogical to mine the merged mining chain (Fantomcoin) only, so the effect on donor chain difficulty is non-existent. This argument only applies when Monero is the merged mining chain.
There were no arguments against Monero being a donor chain.
Of course it is possible.
Also, you can probably just encode the addresses right into the username using commas or something.
However, bear in mind that merged mining with Monero is somewhat illegitimate and a bit of an exploit, since the community voted against it, but amphibian disregarded that and implemented it anyway. Attitudes on the Monero team on the matter range from indifferent to opposed (I'm pretty sure no one actively supports it). So you might be wasting your money if Monero removes support for merged mining, which might happen, though I don't see this as a priority right now. Merged mining support in the pool software could still be used with Bytecoin (and QCN), in any case.
This is simply not true. The proposal the community voted against was to have Monero be a merged mining chain with Bytecoin as the donor chain. Merged mining Monero and Fantomcoin uses Monero as the donor chain and Fantomcoin as the merged mining chain.Also, you can probably just encode the addresses right into the username using commas or something.
However, bear in mind that merged mining with Monero is somewhat illegitimate and a bit of an exploit, since the community voted against it, but amphibian disregarded that and implemented it anyway. Attitudes on the Monero team on the matter range from indifferent to opposed (I'm pretty sure no one actively supports it). So you might be wasting your money if Monero removes support for merged mining, which might happen, though I don't see this as a priority right now. Merged mining support in the pool software could still be used with Bytecoin (and QCN), in any case.
That's arguable. Most (though not all) of the reasons put forward in opposition to merge mining with Bytecoin apply to merge mining with anything else. But it is not arguable that the development team has no interest in supporting it, and it might be removed (though as I said unlikely to happen soon since not a priority), so if merge mining with Monero is a big part of your value proposition, don't waste your money.
However, bear in mind that merged mining with Monero is somewhat illegitimate and a bit of an exploit, since the community voted against it, but amphibian disregarded that and implemented it anyway. Attitudes on the Monero team on the matter range from indifferent to opposed (I'm pretty sure no one actively supports it). So you might be wasting your money if Monero removes support for merged mining, which might happen, though I don't see this as a priority right now. Merged mining support in the pool software could still be used with Bytecoin (and QCN), in any case.
This is simply not true. The proposal the community voted against was to have Monero be a merged mining chain with Bytecoin as the donor chain. Merged mining Monero and Fantomcoin uses Monero as the donor chain and Fantomcoin as the merged mining chain. I am offering a 100 XMR bounty for adding merged mining support into node-cryptonote-pool. I'm thinking the password could be used for FCN address.. Or perhaps a new mining parameter could be added for merged mining addresses?
So it is actually possible ?
Of course it is possible.
Also, you can probably just encode the addresses right into the username using commas or something.
However, bear in mind that merged mining with Monero is somewhat illegitimate and a bit of an exploit, since the community voted against it, but amphibian disregarded that and implemented it anyway. Attitudes on the Monero team on the matter range from indifferent to opposed (I'm pretty sure no one actively supports it). So you might be wasting your money if Monero removes support for merged mining, which might happen, though I don't see this as a priority right now. Merged mining support in the pool software could still be used with Bytecoin (and QCN), in any case.
I am offering a 100 XMR bounty for adding merged mining support into node-cryptonote-pool. I'm thinking the password could be used for FCN address.. Or perhaps a new mining parameter could be added for merged mining addresses?
So it is actually possible ?
I am offering a 100 XMR bounty for adding merged mining support into node-cryptonote-pool. I'm thinking the password could be used for FCN address.. Or perhaps a new mining parameter could be added for merged mining addresses?
I will add some as well. have some other thoughts I will pm you surfer.
I am offering a 100 XMR bounty for adding merged mining support into node-cryptonote-pool. I'm thinking the password could be used for FCN address.. Or perhaps a new mining parameter could be added for merged mining addresses?
98% of the bounty has been paid out, with 49% going to zone117x and 49% to LucasJones.
The addresses were provided to me by tacotime, and the transaction IDs/logs have been provided by me to tacotime.
I'm waiting for payment information to send 2% of the bounty to archit.
The addresses were provided to me by tacotime, and the transaction IDs/logs have been provided by me to tacotime.
I'm waiting for payment information to send 2% of the bounty to archit.
Code:
[wallet 42AiJa]: refresh
Starting refresh...
Height 80401, transaction, received 0.005000000000
Height 80401, transaction, received 0.020000000000
Height 80401, transaction, received 0.900000000000
Height 80401, transaction, received 3.000000000000
Height 80401, transaction, received 70.000000000000
Height 80401, transaction, received 600.000000000000
Height 80401, transaction, received 2000.000000000000
Refresh done, blocks received: 1162
balance: 2673.925000000000, unlocked balance: 2673.925000000000
[wallet 23azyC]: refresh
Starting refresh...
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 0.00295736
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 0.03000000
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 0.70000000
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 8.00000000
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 90.00000000
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 900.00000000
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 4000.00000000
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 10000.00000000
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 800000.00000000
Height 499810, transaction <3edfe80a57687982d88ef37ff673985ba64469f16220ae7c9e986810626e1d43>, received 2000000.00000000
Refresh done, blocks received: 1233
balance: 2814998.73295736, unlocked balance: 2814998.73295736
Date: 11/06/2014 11:22
From: unknown
To: 1CVDT9i4ctZ8rtwuwTDUVVCBEx8KWkPzhn (own address)
Credit: 0.33555 BTC
Net amount: +0.33555 BTC
Transaction ID: 254f55ef41e9160599bee1b3c170ac3d98be924dfaf6b518a41adcdb4d67bdc3
98% of the bounty has been paid out, with 49% going to zone117x and 49% to LucasJones.
The addresses were provided to me by tacotime, and the transaction IDs/logs have been provided by me to tacotime.
I'm waiting for payment information to send 2% of the bounty to archit.
The addresses were provided to me by tacotime, and the transaction IDs/logs have been provided by me to tacotime.
I'm waiting for payment information to send 2% of the bounty to archit.
I received some additional BCN donations. I don't see credit for them being claimed, but if I missed that I apologize.
This brings the BCN total to 5744895.39379054
This brings the BCN total to 5744895.39379054
Just donated 18 MRO 
Hopefully it come soon, we deeply need it !
Hopefully it come soon, we deeply need it !Received this. The 18 was not recorded in the first post so the total is now 5457.
IMPORTANT
I have received a proposal to award 49% of the bounty to zone117x, 49% of the bounty to LucasJones, and 2% to archit.
If there are any objections posted to this thread within 24 hours of this post, I will proceed to request approval of this award plan by majority vote of the identified contributors. If the vote fails, alternative proposals will be considered, again by majority vote.
If there are no objections posted to this thread within 24 hours of this post, I will distribute the bounty accordingly.
Was the bounty distributed?I have received a proposal to award 49% of the bounty to zone117x, 49% of the bounty to LucasJones, and 2% to archit.
If there are any objections posted to this thread within 24 hours of this post, I will proceed to request approval of this award plan by majority vote of the identified contributors. If the vote fails, alternative proposals will be considered, again by majority vote.
If there are no objections posted to this thread within 24 hours of this post, I will distribute the bounty accordingly.
Not yet, but will go out soon (as soon as I am at a location with access to the wallets)
IMPORTANT
I have received a proposal to award 49% of the bounty to zone117x, 49% of the bounty to LucasJones, and 2% to archit.
If there are any objections posted to this thread within 24 hours of this post, I will proceed to request approval of this award plan by majority vote of the identified contributors. If the vote fails, alternative proposals will be considered, again by majority vote.
If there are no objections posted to this thread within 24 hours of this post, I will distribute the bounty accordingly.
Was the bounty distributed? I have received a proposal to award 49% of the bounty to zone117x, 49% of the bounty to LucasJones, and 2% to archit.
If there are any objections posted to this thread within 24 hours of this post, I will proceed to request approval of this award plan by majority vote of the identified contributors. If the vote fails, alternative proposals will be considered, again by majority vote.
If there are no objections posted to this thread within 24 hours of this post, I will distribute the bounty accordingly.
Jump to: