Search content
Sort by
Showing 20 of 46 results by ntkrnl
nxt is not a scam
Code:
static void matchOrders(long paramLong)
throws Exception {
TreeSet localTreeSet1 = (TreeSet) sortedAskOrders.get(Long.valueOf(paramLong));
TreeSet localTreeSet2 = (TreeSet) sortedBidOrders.get(Long.valueOf(paramLong));
synchronized (askOrders) {
synchronized (bidOrders) {
do {
Nxt.AskOrder localAskOrder = (Nxt.AskOrder) localTreeSet1.first();
Nxt.BidOrder localBidOrder = (Nxt.BidOrder) localTreeSet2.first();
if (localAskOrder.price > localBidOrder.price) {
break;
}
int i = localAskOrder.quantity < localBidOrder.quantity ? localAskOrder.quantity : localBidOrder.quantity;
long l = (localAskOrder.height < localBidOrder.height) || ((localAskOrder.height == localBidOrder.height) && (localAskOrder.id < localBidOrder.id)) ? localAskOrder.price : localBidOrder.price;
if (localAskOrder.quantity -= i == 0) {
askOrders.remove(Long.valueOf(localAskOrder.id));
localTreeSet1.remove(localAskOrder);
}
synchronized (localAskOrder.account) {
localAskOrder.account.setBalance(localAskOrder.account.balance + i * l);
localAskOrder.account.setUnconfirmedBalance(localAskOrder.account.unconfirmedBalance + i * l);
}
if (localBidOrder.quantity -= i == 0) {
bidOrders.remove(Long.valueOf(localBidOrder.id));
localTreeSet2.remove(localBidOrder);
}
synchronized (localBidOrder.account) {
Integer localInteger = (Integer) localBidOrder.account.assetBalances.get(Long.valueOf(paramLong));
if (localInteger == null) {
localBidOrder.account.assetBalances.put(Long.valueOf(paramLong), Integer.valueOf(i));
localBidOrder.account.unconfirmedAssetBalances.put(Long.valueOf(paramLong), Integer.valueOf(i));
} else {
localBidOrder.account.assetBalances.put(Long.valueOf(paramLong), Integer.valueOf(localInteger.intValue() + i));
localBidOrder.account.unconfirmedAssetBalances.put(Long.valueOf(paramLong), Integer.valueOf(((Integer) localBidOrder.account.unconfirmedAssetBalances.get(Long.valueOf(paramLong))).intValue() + i));
}
}
if (localTreeSet1.isEmpty()) {
break;
}
} while (!localTreeSet2.isEmpty());
}
}
}
throws Exception {
TreeSet localTreeSet1 = (TreeSet) sortedAskOrders.get(Long.valueOf(paramLong));
TreeSet localTreeSet2 = (TreeSet) sortedBidOrders.get(Long.valueOf(paramLong));
synchronized (askOrders) {
synchronized (bidOrders) {
do {
Nxt.AskOrder localAskOrder = (Nxt.AskOrder) localTreeSet1.first();
Nxt.BidOrder localBidOrder = (Nxt.BidOrder) localTreeSet2.first();
if (localAskOrder.price > localBidOrder.price) {
break;
}
int i = localAskOrder.quantity < localBidOrder.quantity ? localAskOrder.quantity : localBidOrder.quantity;
long l = (localAskOrder.height < localBidOrder.height) || ((localAskOrder.height == localBidOrder.height) && (localAskOrder.id < localBidOrder.id)) ? localAskOrder.price : localBidOrder.price;
if (localAskOrder.quantity -= i == 0) {
askOrders.remove(Long.valueOf(localAskOrder.id));
localTreeSet1.remove(localAskOrder);
}
synchronized (localAskOrder.account) {
localAskOrder.account.setBalance(localAskOrder.account.balance + i * l);
localAskOrder.account.setUnconfirmedBalance(localAskOrder.account.unconfirmedBalance + i * l);
}
if (localBidOrder.quantity -= i == 0) {
bidOrders.remove(Long.valueOf(localBidOrder.id));
localTreeSet2.remove(localBidOrder);
}
synchronized (localBidOrder.account) {
Integer localInteger = (Integer) localBidOrder.account.assetBalances.get(Long.valueOf(paramLong));
if (localInteger == null) {
localBidOrder.account.assetBalances.put(Long.valueOf(paramLong), Integer.valueOf(i));
localBidOrder.account.unconfirmedAssetBalances.put(Long.valueOf(paramLong), Integer.valueOf(i));
} else {
localBidOrder.account.assetBalances.put(Long.valueOf(paramLong), Integer.valueOf(localInteger.intValue() + i));
localBidOrder.account.unconfirmedAssetBalances.put(Long.valueOf(paramLong), Integer.valueOf(((Integer) localBidOrder.account.unconfirmedAssetBalances.get(Long.valueOf(paramLong))).intValue() + i));
}
}
if (localTreeSet1.isEmpty()) {
break;
}
} while (!localTreeSet2.isEmpty());
}
}
}
NXT is very features, But the client can upgrade more easy to use?
It will be something like this, but I don't know when they will launch it. Maybe 3rd january?
Can you confirm CfB?
http://87.230.14.1/charts/01_screen.png
url?
白皮书见：http://8btc.com/thread-808-1-1.html
3i公司连续两次融资没做出什么像样的产品来不说还要进行第三轮融资
而论坛上对这个项目的质疑也越来越大
典型的问题是，所谓的bitUSD如何和实物usd交割？ （https://bitcointalk.org/index.php?topic=279771.420）
本来去中心化的交易所就是为了解决虚拟货币和法币接口问题
也就是现货交易
结果他搞了个无法交割的期货交易
最终bitUSD需要靠线下或者商家去买卖
而线下或者商家去买卖又反而存在信任问题（无法一手交钱一手交货，存在第三方）
于是什么也没解决
mastercoin项目募资了一大堆钱没搞定（项目负责人整天在社区里面问别人要代码）
至少人家账目清晰，有情可原
bitshares protoshares更像是画饼充饥卖概念
PS：有人可能会说keyhotee算个产品
好吧，这个namecoin+bitmessage的玩意儿最多是个整合，创新不算太大
对比特币协议有所了解的人很短时间内就能拼凑起代码来的
3i公司连续两次融资没做出什么像样的产品来不说还要进行第三轮融资
而论坛上对这个项目的质疑也越来越大
典型的问题是，所谓的bitUSD如何和实物usd交割？ （https://bitcointalk.org/index.php?topic=279771.420）
本来去中心化的交易所就是为了解决虚拟货币和法币接口问题
也就是现货交易
结果他搞了个无法交割的期货交易
最终bitUSD需要靠线下或者商家去买卖
而线下或者商家去买卖又反而存在信任问题（无法一手交钱一手交货，存在第三方）
于是什么也没解决
mastercoin项目募资了一大堆钱没搞定（项目负责人整天在社区里面问别人要代码）
至少人家账目清晰，有情可原
bitshares protoshares更像是画饼充饥卖概念
PS：有人可能会说keyhotee算个产品
好吧，这个namecoin+bitmessage的玩意儿最多是个整合，创新不算太大
对比特币协议有所了解的人很短时间内就能拼凑起代码来的
It seems like you are running a wrong version, please get the lastest source from github to join the main yac p2pool, the hashrate of which is 20m/s.
Pool appears to be down. Will it be back up soon?
Any other decent YAC pools out there?
Any other decent YAC pools out there?
I've rebuilt the server.
Very sorry for the troubles brought to you.
I think we should collect all yacoin p2pool into the main thread.
Just to let you guys know, I've started integrating other cryptos into my pool. I've put a 2% fee on other chains, but keeping the YACoin fee at 0%. 
You can keep your miners pointed at yac.procrypto.com:8336 and they'll still be fine.
Could have been someone testing their GPU setup of course.
You can keep your miners pointed at yac.procrypto.com:8336 and they'll still be fine.
This address probably ripped p2pool YAC miners from payout because of bug in earlier versions:
http://yacexplorer.tk/address/Y6Qcc77xaX4BFiBpEbMTPhunzii2UzkYtJ
I think he just rend some ec2 instances, because the 100m hashrate came so suddenly and disappeared completely in a very short time.http://yacexplorer.tk/address/Y6Qcc77xaX4BFiBpEbMTPhunzii2UzkYtJ
Could have been someone testing their GPU setup of course.
I don't think so.
After the 100m hashrate disappeared, it didn't go to yac.dontmine.me, which is known as the biggest yac pool, in fact, the total hashrate of yac.dontmine.me had a big drop several days ago, perhaps because some miners went to wdc pool. There is probably a gpu miner, but I'm sure it's not popular.
This address probably ripped p2pool YAC miners from payout because of bug in earlier versions:
http://yacexplorer.tk/address/Y6Qcc77xaX4BFiBpEbMTPhunzii2UzkYtJ
http://yacexplorer.tk/address/Y6Qcc77xaX4BFiBpEbMTPhunzii2UzkYtJ
I think he just rend some ec2 instances, because the 100m hashrate came so suddenly and disappeared completely in a very short time.
Re: [ANN][YAC] YACoin ongoing development - Unofficial client fork
I compiled a version of win64 from windmaster's git branch, if you have 64-bit windows installed, you can try it.
http://sourceforge.net/projects/hnindev/files/yacoin-qt-0.4.0.0-g32a928e-winx64.zip
nice workhttp://sourceforge.net/projects/hnindev/files/yacoin-qt-0.4.0.0-g32a928e-winx64.zip
Bit confused, graphs page shows "Current payout to default address" as a few fractions of a YAC, however, I've set the fees to 0% and I'm the only person mining on my own node right now. I thought this amount should show as zero.
Any help OP? Why does it show this amount?
Any help OP? Why does it show this amount?
Yeah, here is the reason:
The broken code on github hasn't been updated in 3 days.
What's the progress?
What's the progress?
It's OK now.
Thanks, that seems to be working.
Is there anyway to set the default payout address or is that removed?
In the POS(PROOF OF STACK) featured coin, when a block is mined, and submitted to the client, it must be signed with your public key, while bitcoin/litecoin don't have to. That' why novacoin p2pool delete "-address" option. Because when you specify an address, it's just a hash160(pubkey), not your publish key, yacoind will throw an error "sign block failed".
In the lastest version of yacoin-p2pool, no matter what the "fee" is, the host user of p2pool will be paid at least 0.01, just for the pubkey, without this, you can never sign a block.
So, if you want to specify an individual address, use the worker-name-as-address mode.
UPDATE:
mmh, there is still something wrong with the payment system
In other words, ppcoin novacoin yacoin basiclly don't support paid-by-worker mode( -u username as address). You can only run p2pool minerd yacoind on your own machine and pay to yourselft.
mmh, there is still something wrong with the payment system
In other words, ppcoin novacoin yacoin basiclly don't support paid-by-worker mode( -u username as address). You can only run p2pool minerd yacoind on your own machine and pay to yourselft.
So if I've been running this P2Pool on my server overnight, connected miners in the usual P2Pool way (address as username, any password), and found a couple of blocks, where would the payouts have gone to?
Also, for a complete noob like me, how do I go about changing my setup for now, so that all work goes towards the single wallet address on my server?
Thanks for your help.. will definitely be giving you a solid tip once the teething problems are fixed.
In fact, if you choose the address-as-name mode, you got nothing, the block was not successfully submitted with an error "Sign failed" in /.yacoin/debug.log
Here is some technical details:
1.Compared with bitcoin litecoin, there is a quite different feature in ppcoin novacoin yacoin . If a block is found, the p2pool will call a jsonprc method called "submitblock", here is the "submitblock" funtion in yacoin
's source:
Code:
// ppcoin: sign block
bool CBlock::SignBlock(const CKeyStore& keystore)
{
vector vSolutions;
txnouttype whichType;
if(!IsProofOfStake())
{
for(unsigned int i = 0; i < vtx[0].vout.size(); i++)
{
const CTxOut& txout = vtx[0].vout[i];
if (!Solver(txout.scriptPubKey, whichType, vSolutions))
continue;
if (whichType == TX_PUBKEY)
{
// Sign
valtype& vchPubKey = vSolutions[0];
CKey key;
if (!keystore.GetKey(Hash160(vchPubKey), key))
continue;
if (key.GetPubKey() != vchPubKey)
continue;
if(!key.Sign(GetHash(), vchBlockSig))
continue;
return true;
}
}
}
else
{
const CTxOut& txout = vtx[1].vout[1];
if (!Solver(txout.scriptPubKey, whichType, vSolutions))
return false;
if (whichType == TX_PUBKEY)
{
// Sign
valtype& vchPubKey = vSolutions[0];
CKey key;
if (!keystore.GetKey(Hash160(vchPubKey), key))
return false;
if (key.GetPubKey() != vchPubKey)
return false;
return key.Sign(GetHash(), vchBlockSig);
}
}
[color=red] printf("Sign failed\n");[/color]
return false;
}
bool CBlock::SignBlock(const CKeyStore& keystore)
{
vector vSolutions;
txnouttype whichType;
if(!IsProofOfStake())
{
for(unsigned int i = 0; i < vtx[0].vout.size(); i++)
{
const CTxOut& txout = vtx[0].vout[i];
if (!Solver(txout.scriptPubKey, whichType, vSolutions))
continue;
if (whichType == TX_PUBKEY)
{
// Sign
valtype& vchPubKey = vSolutions[0];
CKey key;
if (!keystore.GetKey(Hash160(vchPubKey), key))
continue;
if (key.GetPubKey() != vchPubKey)
continue;
if(!key.Sign(GetHash(), vchBlockSig))
continue;
return true;
}
}
}
else
{
const CTxOut& txout = vtx[1].vout[1];
if (!Solver(txout.scriptPubKey, whichType, vSolutions))
return false;
if (whichType == TX_PUBKEY)
{
// Sign
valtype& vchPubKey = vSolutions[0];
CKey key;
if (!keystore.GetKey(Hash160(vchPubKey), key))
return false;
if (key.GetPubKey() != vchPubKey)
return false;
return key.Sign(GetHash(), vchBlockSig);
}
}
[color=red] printf("Sign failed\n");[/color]
return false;
}
The variable "keystore" is the keys(pubkey pubkey_hash privatekey etc.) of your wallet. That means if you submit a block, you should sign it up with the pubkeys from your wallet, but username-as-address mode just only sends p2pool your pubkey_hash. you can easily get a pubkey_hash with an address, but never get pubkey, just like you want to get the text password from md5.
I've already found a tricky way to fix this problem, just wait for the next version
What is the weakest link or bottleneck when running P2Pool? I guess RAM but I would not bet on that, LOL, I actualy don't even know how pool works behind the scene but I'll need
to learn or find someone trustable to do it for me. I would like to do it with classic pool and PPS payout system though so that miners can use YAC as soon as they submitted share.
to learn or find someone trustable to do it for me. I would like to do it with classic pool and PPS payout system though so that miners can use YAC as soon as they submitted share.
Not sure as yet, will monitor it. Doesn't really appear to use much RAM or CPU power though (circa 55MB RAM for p2pool, 85MB for yacoind and minimal CPU use at current load).
My node is going well, hashrate is decent and we've been picking up a few blocks. Throw all of your might at it, and we could be doing well!
Would the OP consider updating his post with the current live nodes and their fee structures?
pypy may be helpful to reduce the cpu usage. There is a memory leak in P2PoolExtendedFrontEnd, and jquery & bootstrap lib should be speeded up with a CDN. This will be fixed in the next version.
The main thread is updated, please download the lastest source or binary, this time we'll be really mining in only one pool.
Quote
NO, it's a bug.
The newest protocol conflicts with the old one, that's why I changed the server to the new version, and changed back again.
We must use a new port and a new protocol prefix. I have update the source on github a moment ago. Please download the newest one.
https://github.com/cctvsmg/yacoin-p2pool
the newest version use a port 8338 like:
http://pool.bitcn.org:8338
The newest protocol conflicts with the old one, that's why I changed the server to the new version, and changed back again.
We must use a new port and a new protocol prefix. I have update the source on github a moment ago. Please download the newest one.
https://github.com/cctvsmg/yacoin-p2pool
the newest version use a port 8338 like:
http://pool.bitcn.org:8338
I've got all the bugs sorted on my node now, so if you want to mine some YAC on a good solid server then head over to.....
--url http://mining.bitvolcano.com:8338
--user youryacaddress
--pass x
Remember to use the latest cpuminer with the -a scrypt-jane option
There is a 1% fee.
Stats are at http://bitvolcano.com:8338
--url http://mining.bitvolcano.com:8338
--user youryacaddress
--pass x
Remember to use the latest cpuminer with the -a scrypt-jane option
There is a 1% fee.
Stats are at http://bitvolcano.com:8338
Take out that addition you don't need it, the peers are propagated though the net from the boot node.
Ok, cool. Have updated to the latest code and restarted p2pool.
http://yac.procrypto.com:8080/ - 0% fee, 0% to author.
Solid server with pro host in top data centre.
Also throwing a few (loss making) server instances at it to get the hashrate up.
The lastest version seems to be working very well, the hash "00000000060a41a3dac8ffa43c30d09372b73be0a841804e9ffdc00078d43059" can be found in the blockchain.
not sure if this is normal, as I'm not that familar with p2pool right now:
this comes around every 5 seconds..
and another question:
if I run on a windwos host a miner minerd_scrypt_jane_x64 i got this:
is this OK?
Code:
utgoing connection to peer 91.235.254.37:9355 established. p2pool version: 1100 'b2de428-dirty'
2013-05-16 10:45:21.310680 Sending 1 shares to 91.235.254.37:9355
2013-05-16 10:45:21.364218 Peer sent entire transaction d569d639cecd98d005c22dc854f2eea8be35ab5c7c6c66dae82338cf136c0afe that was already received
2013-05-16 10:45:21.375079 Lost peer 91.235.254.37:9355 - Connection was closed cleanly.
2013-05-16 10:45:21.375517 > in handle_share_hashes:
2013-05-16 10:45:21.375557 > Traceback (most recent call last):
2013-05-16 10:45:21.375591 > Failure: twisted.internet.error.ConnectionDone: Connection was closed cleanly.
2013-05-16 10:45:21.310680 Sending 1 shares to 91.235.254.37:9355
2013-05-16 10:45:21.364218 Peer sent entire transaction d569d639cecd98d005c22dc854f2eea8be35ab5c7c6c66dae82338cf136c0afe that was already received
2013-05-16 10:45:21.375079 Lost peer 91.235.254.37:9355 - Connection was closed cleanly.
2013-05-16 10:45:21.375517 > in handle_share_hashes:
2013-05-16 10:45:21.375557 > Traceback (most recent call last):
2013-05-16 10:45:21.375591 > Failure: twisted.internet.error.ConnectionDone: Connection was closed cleanly.
this comes around every 5 seconds..
and another question:
if I run on a windwos host a miner minerd_scrypt_jane_x64 i got this:
Code:
Worker a submitted share with hash > target:
2013-05-16 10:47:14.835635 Hash: 3cdb25c5746ad9ff4a5002b135160be5a0351dc07b9c62bbe853364b20b4f9e8
2013-05-16 10:47:14.835676 Target: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
2013-05-16 10:47:14.835635 Hash: 3cdb25c5746ad9ff4a5002b135160be5a0351dc07b9c62bbe853364b20b4f9e8
2013-05-16 10:47:14.835676 Target: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
is this OK?
NO, it's a bug.
The lastest protocol conflicts with the former one, that's why I changed the server to the new version, and changed back again.
We must use a new port and a new protocol prefix. I have update the source on github a moment ago. Please download the newest one.
https://github.com/cctvsmg/yacoin-p2pool
the newest version use a port 8338 like:
http://pool.bitcn.org:8338
The broken code on github hasn't been updated in 3 days.
What's the progress?
What's the progress?
It's OK now.
Pls add me on run: -n rav3n.dtdns.net:9355
I'm down too.
"lost contact with bitcoind"
Sorry, I'm debugging the server.
The broken code on github hasn't been updated in 3 days.
What's the progress?
What's the progress?
It's OK now.
Thanks, that seems to be working.
Is there anyway to set the default payout address or is that removed?
In the POS(PROOF OF STACK) featured coin, when a block is mined, and submitted to the client, it must be signed with your public key, while bitcoin/litecoin don't have to. That' why novacoin p2pool delete "-address" option. Because when you specify an address, it's just a hash160(pubkey), not your publish key, yacoind will throw an error "sign block failed".
In the lastest version of yacoin-p2pool, no matter what the "fee" is, the host user of p2pool will be paid at least 0.01, just for the pubkey, without this, you can never sign a block.
So, if you want to specify an individual address, use the worker-name-as-address mode.
The broken code on github hasn't been updated in 3 days.
What's the progress?
What's the progress?
It's OK now.