borris123
|
|
August 29, 2015, 12:40:25 PM |
|
I have a questions regarding mining a local network of mixed gpu and cpu. I am mining 1 wallet locally i.e pointing miners on local network to 10.0.0.* 9325 . Are there any beneficial conf settings that should be invoked while mixed method (GPU?CPU to same wallet) mining? Or local network wallet mining? I also noted a significant drop off in block finding after about 4 hours which coincided with the wallets Genesis block. Perhaps this is normal, or just luck? Thanks. An additional thought... when gpu mining directly to a wallet, is it more efficient to have for example 3 gpu's in 1 comp than to have 3 separately mining that same wallet?? Obviously this applies to me and I have wondered this about any networks I have mined. And does cpu mining while gpu mining on the same comp affect efficiency of the gpu...it does not appear to according to the output, but....?? Thank you for any info Update regarding finding blocks: Since noting the lack of finding blocks after Genesis block as stated in post above, I restarted wallet and normal production seems to have resumed (not that I have any data to compare to other than production prior to Genesis block). Hopefully someone can still give some insight into my above questions and perhaps my observed "bug" helps others. I have not found any blocks only trust transactions and I got a fair bit staking. Is this normal? What are you mining with?? Staking not mining. Thought u got blocks that way as well? Or am I wrong?
|
|
|
|
Namsbreh
|
|
August 30, 2015, 08:38:24 PM |
|
Staking not mining. Thought u got blocks that way as well? Or am I wrong?
Wrong I'm afraid. There are no blocks as well, just the trust & genisis transactions.
|
|
|
|
AliMan
|
|
August 31, 2015, 10:34:58 AM |
|
Anyone reach 100% trust weight by now?
|
|
|
|
sulfurtank
|
|
August 31, 2015, 12:37:35 PM |
|
Honestly, looking at it the most active times of development is the biggest time of price fall + accumulation periods. When development is quiet and nothing much is going on, the price tends to go up.
|
|
|
|
merc84
|
|
August 31, 2015, 01:30:08 PM |
|
Anyone reach 100% trust weight by now?
Yes i have 100% trust weight.
|
|
|
|
BitcoinSanDiego
|
|
August 31, 2015, 04:36:44 PM |
|
WTB: 1BTC of Niro @ 500 satoshis
|
|
|
|
|
BitcoinSanDiego
|
|
August 31, 2015, 05:35:10 PM |
|
Can you fill an order if I place it? Or are you just being a smart ass? I'm not going to buy coins at asking price when there is no buy support.
|
|
|
|
macorcina
|
|
August 31, 2015, 05:39:28 PM |
|
Can you fill an order if I place it? Or are you just being a smart ass? I'm not going to buy coins at asking price when there is no buy support. make buy order and watch
|
|
|
|
|
Videlicet
Legendary
Offline
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
|
|
August 31, 2015, 07:02:57 PM Last edit: August 31, 2015, 09:00:24 PM by Videlicet |
|
I'll take a look into the CPU/GPU possible conflicts with nPoS. Thanks for letting me know, as to mining either channel on the same wallet that works just the same as adding another worker for the same channel, the LLP handles either channel perfectly fine. As to nPoS Genesis and Trust transactions are linked as the first transaction on the block in which you produce, so nPoS is producing blocks and processing third party transactions. Genesis transactions linked to the first block your trust key creates is not allowed by the rules of Nexus to process any transactions to thwart any attackers attempt to attack nPoS using genesis transactions, so once your trust begins to be established in the network, you then become capable of helping process transactions. Think of Trust and Genesis transactions as replacements for the coinbase transaction that miners produce with blocks. A nPoS block cannot be produced without the first transaction being Genesis or Trust, which is marked in the script signature with a fibonacci byte series. Trust transactions then have to root their first input with the hash of their trust key to tie their genesis transaction to all following Trust blocks. Keep posted for Nexus 0.2.1 which I will be releasing as soon as I get internet setup in my new house. From there Nexus 0.2.2 will incorporate updates to the presentation of the wallet, 0.2.1 will be modifications to the rules to tune nPoS to a better acclimate a wider range of users such as increased stake rate up to 5%, 21 day expiration. This update will be mandatory, most likely with activation being 2 weeks from release so Bittrex can have time to update, last update was difficult to get to them in one week since they are usually fairly busy. Anything else let me know Thank You,Viz.
|
[ Nexus] Created by Viz. [ Videlicet] : "videre licet - it may be seen; evidently; clearly"
|
|
|
BitcoinSanDiego
|
|
September 01, 2015, 12:55:18 AM |
|
I'll take a look into the CPU/GPU possible conflicts with nPoS. Thanks for letting me know, as to mining either channel on the same wallet that works just the same as adding another worker for the same channel, the LLP handles either channel perfectly fine. As to nPoS Genesis and Trust transactions are linked as the first transaction on the block in which you produce, so nPoS is producing blocks and processing third party transactions. Genesis transactions linked to the first block your trust key creates is not allowed by the rules of Nexus to process any transactions to thwart any attackers attempt to attack nPoS using genesis transactions, so once your trust begins to be established in the network, you then become capable of helping process transactions. Think of Trust and Genesis transactions as replacements for the coinbase transaction that miners produce with blocks. A nPoS block cannot be produced without the first transaction being Genesis or Trust, which is marked in the script signature with a fibonacci byte series. Trust transactions then have to root their first input with the hash of their trust key to tie their genesis transaction to all following Trust blocks. Keep posted for Nexus 0.2.1 which I will be releasing as soon as I get internet setup in my new house. From there Nexus 0.2.2 will incorporate updates to the presentation of the wallet, 0.2.1 will be modifications to the rules to tune nPoS to a better acclimate a wider range of users such as increased stake rate up to 5%, 21 day expiration. This update will be mandatory, most likely with activation being 2 weeks from release so Bittrex can have time to update, last update was difficult to get to them in one week since they are usually fairly busy. Anything else let me know Thank You,Viz.Can we get a Mac build of the wallet?
|
|
|
|
COOLERbyPSP
Member
Offline
Activity: 124
Merit: 10
|
|
September 01, 2015, 01:11:53 AM |
|
Anybody can give me a link to NVIDIA miner? Compiled for windows (8.1 x64) Just bought GTX960 and want to tet it
|
|
|
|
BitcoinSanDiego
|
|
September 01, 2015, 03:27:42 AM |
|
Anybody can give me a link to NVIDIA miner? Compiled for windows (8.1 x64) Just bought GTX960 and want to tet it This is all I could find: http://nexusniro.com/?tab=DownloadYo man you gotta update your signature
|
|
|
|
BitcoinSanDiego
|
|
September 01, 2015, 03:39:01 AM |
|
I'll take a look into the CPU/GPU possible conflicts with nPoS. Thanks for letting me know, as to mining either channel on the same wallet that works just the same as adding another worker for the same channel, the LLP handles either channel perfectly fine. As to nPoS Genesis and Trust transactions are linked as the first transaction on the block in which you produce, so nPoS is producing blocks and processing third party transactions. Genesis transactions linked to the first block your trust key creates is not allowed by the rules of Nexus to process any transactions to thwart any attackers attempt to attack nPoS using genesis transactions, so once your trust begins to be established in the network, you then become capable of helping process transactions. Think of Trust and Genesis transactions as replacements for the coinbase transaction that miners produce with blocks. A nPoS block cannot be produced without the first transaction being Genesis or Trust, which is marked in the script signature with a fibonacci byte series. Trust transactions then have to root their first input with the hash of their trust key to tie their genesis transaction to all following Trust blocks. Keep posted for Nexus 0.2.1 which I will be releasing as soon as I get internet setup in my new house. From there Nexus 0.2.2 will incorporate updates to the presentation of the wallet, 0.2.1 will be modifications to the rules to tune nPoS to a better acclimate a wider range of users such as increased stake rate up to 5%, 21 day expiration. This update will be mandatory, most likely with activation being 2 weeks from release so Bittrex can have time to update, last update was difficult to get to them in one week since they are usually fairly busy. Anything else let me know Thank You,Viz.It seems to me that "instant" transactions are trivial really, given that they have a huge cost of either a) centralization and centralized points of failure and b) network security Although, with the trust key system you've developed, at this point it seems it would be not very difficult to give nodes with a certain trust level the ability to sign transactions instantly to validate them. I am not advocating this, but this would be a pretty simple extension into the territory of Darkcoin. I personally don't think we need instant transactions because of the centralization and network security risks. I am very interested to see how the Lightening network will take transactions off-blockchain for Bitcoin and provide a settlement service that can be anchored into blocks. This seems like a better balance because it affords people the option of using outside services or centralized services, but not risking the integrity of the network with such idealistic naivete
|
|
|
|
BitcoinSanDiego
|
|
September 01, 2015, 03:48:33 AM |
|
Another request, can you open-source the code with the launch of the company and revealing identity. I want to get more developers to come and help build on top of this protocol.
|
|
|
|
KryptoKash (OP)
Sr. Member
Offline
Activity: 519
Merit: 275
YeBit: Affiliate Powered Token Sales & Airdrops
|
|
September 01, 2015, 04:17:28 AM |
|
Our designer just resurfaced he went on vacation apparently, new OP should be done next few days with a bit more updates as far as the order of which features are going to be pushed out.
|
...
|
|
|
macorcina
|
|
September 01, 2015, 05:28:39 PM |
|
pay off button for pool
|
|
|
|
Videlicet
Legendary
Offline
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
|
|
September 01, 2015, 06:15:46 PM |
|
Well instant transactions will happen with levels of security by what I call the Block Tree where transactions can process on their own branches allowing simultaneous processing as each channel forms their trunks, and the limbs to scale the tree based on transaction necessity so in essence the blockchain and production will only scale based on the volume of transactions. The trust network that is becoming formed with trust keys will grow into the core of the network, to allow light nodes to function without needing to sync, so forth.
The block tree will also allow the merging system to take form, so instead of worrying about one chain, we'll see our blockchain grow into a tree as I split the channels, as of right now we are building the solid trunk. Consider it a sophisticated use of side chains, but instead of being a chain on the side, it will be a chain formed from the trunk, to then create the mint upon that branch and causing transactions created from that limb to be processed on that limb, so that as more limbs start to take form, our ability to process transactions simultaneously will increase its capacity.
Thank You, Viz.
|
[ Nexus] Created by Viz. [ Videlicet] : "videre licet - it may be seen; evidently; clearly"
|
|
|
Namsbreh
|
|
September 01, 2015, 07:20:04 PM |
|
Our designer just resurfaced he went on vacation apparently, new OP should be done next few days with a bit more updates as far as the order of which features are going to be pushed out. FFS, sack the lazy sod! It is my understanding that this designer is being paid to do the OP. If so, he should not have gone away leaving the OP half done with missing info etc. Just my opinion.
|
|
|
|
|