Search content
Sort by
Showing 20 of 248 results by bitsolutions
I found an exploit that can be used to enable SSH https://twitter.com/james_hilliard/status/1095225270011781120.
So I went ahead and attempted this OS install.
1st problem: quick guide is not very descriptive! For instance, the requirement to get the control board on the T1 to recognize your SD card requires you to adjust the jumpers on the control board. No guide is given on this besides J1 0 1. I removed the control board from my T1 to get a good look at the jumpers (had to try and find them as no guidance was given on where they were on the board). Upon finding them I had no idea what to do from there or even how to adjust it to make its status 0 1. This is could simply be from my lack of hardware experience.
2nd problem: There is no SD card reader on the T1 control board. From what I can gather from the quick guide, this OS install is predicated upon using the SD card slot. So this is a hard stop and I'm not sure how to proceed.
Can the Braiins team please provide more detailed instructions, like a video perhaps, on the complete, step-by-step process to get the Braiins OS installed on our machines?
1st problem: quick guide is not very descriptive! For instance, the requirement to get the control board on the T1 to recognize your SD card requires you to adjust the jumpers on the control board. No guide is given on this besides J1 0 1. I removed the control board from my T1 to get a good look at the jumpers (had to try and find them as no guidance was given on where they were on the board). Upon finding them I had no idea what to do from there or even how to adjust it to make its status 0 1. This is could simply be from my lack of hardware experience.
2nd problem: There is no SD card reader on the T1 control board. From what I can gather from the quick guide, this OS install is predicated upon using the SD card slot. So this is a hard stop and I'm not sure how to proceed.
Can the Braiins team please provide more detailed instructions, like a video perhaps, on the complete, step-by-step process to get the Braiins OS installed on our machines?
Yeah, this isn't going to flash easily on production T1's since those don't have SD card slots.
⭐ Merited by frodocooper (1)
I dug into it. It is just a modded bmminer like my firmware and many others. The different is their firmware flash they built replaces the interface web files with their customs ones that make it look all fancy. So it's the same thing.
No, you're looking at the wrong branch, their cgminer for S9 is different from their one for dragon T1.
⭐ Merited by frodocooper (2)
Good luck... No one has been able to complete the install yet
Yeah, it can't really be flashed by end users since production units don't have SD card slots. Probably also high chance of causing damage since I don't think it properly handles all hashboard variants(I skimmed their cgminer code and it appears to be missing the code for handling the different hashboard VID variants).
Re: Dollemizer Firmware ASICBOOST Comming! [custom s9, s9i, t9 Firmware upgrade]
The GPLv3 states that you need to show us that you run our software and then we can send you the source code. We do not have to make the source code public.
If you would like the source code, send us that you are running our software and share your contact details.
If you would like the source code, send us that you are running our software and share your contact details.
I've never heard of a GPLv3 requirement to run it(if there is one please point me to the specific line in the GPLv3 license), GPLv3 requirements are based on distribution of the software(ie downloading it) not running it. You can contact me via PM.
Here's proof I downloaded it:
Code:
$ shasum -a 256 Dollemizer875-USA.gz
ee4386b018901799c205788bf0fb15db21b1599e4c4bf3a0d2e6abdd1d618d7e Dollemizer875-USA.gz
ee4386b018901799c205788bf0fb15db21b1599e4c4bf3a0d2e6abdd1d618d7e Dollemizer875-USA.gz
Re: Dollemizer Firmware ASICBOOST Comming! [custom s9, s9i, t9 Firmware upgrade]
Thank you for your interest.
If you could please specify your request, that would be very helpful.
If you could please specify your request, that would be very helpful.
The cgminer source code (cgminer/bmminer) is GPLv3 licensed which requires you provide the source code upon request.
⭐ Merited by lightfoot (1)
The reset button on these only power cycles the controller, it does not touch the config at all.
Here is what the ip set button does:
When using the ip set button to set to static it should set the miner to the following IP settings:
Here is what the ip set button does:
Code:
1-5 second button press = send locator packet
5-15 second button press = full factory reset(this will also result in IP being reset to DHCP)
15-30 second button press = change IP mode between DHCP and static
5-15 second button press = full factory reset(this will also result in IP being reset to DHCP)
15-30 second button press = change IP mode between DHCP and static
When using the ip set button to set to static it should set the miner to the following IP settings:
Code:
IP address: 192.168.1.254
netmask: 255.255.255.0
gateway: 192.168.1.1
primary DNS: 8.8.8.8
secondary DNS: 114.114.114.114
netmask: 255.255.255.0
gateway: 192.168.1.1
primary DNS: 8.8.8.8
secondary DNS: 114.114.114.114
Hi All,
I wasn't aware of the GPL license, so I did some investigation last days. After reading the GPL licenses I can conclude that stangerm2 is right. So that means I do have to provide the modified sources as most of the current modifications are now build on top of a linked module in cgminer.
There are some consequences in releasing the source though:
- As far as I know, Bitmain is free to use these improvements in their current and their new products they will sell. I do hope they compensate these free goodies with a multi algorithm D3 firmware one day
- There will probably appear modified firmware binaries which can cause damaging your miners if the maker doesn't know what he's doing...
- I had plans to buy a S9 as there are a lot of requests and make a modified S9 version, but I might consider not to jump on that boat for now. (let's first see what will happen with the D3)
Legit alternatives instead of releasing the sourcecode
- I stop this project and take the binaries offline. I don't like this option, as the whole idea is to help improve the situations for the D3 owners.
- Temporary I take the binaries offline and I will write something from scratch / not linked to the sources of cgminer. This will take away the consequences, but a lot of time and effort (at least a month or two) will be put into something that will probably not lead to any improvements for you guys.
My proposal
- Although these consequences I will release source of a stable version (non BETA) that allow others to investigate the voltage / fan mods / fault check improvements I did. (devfee related code will be removed from the source). This allow others to look into the changes I did to make a binary for themselves without devfee.
BETA functionality will be left out of the source right now since it's not yet stable and will create dangerous situations when used in a wrong way. I might have to restrict the use of a BETA versions to a closed group instead of providing a public link to the BETA versions.
Happy mining
Ciao Blissz
To add some encouragement to getting the source released, I'll be issuing a DMCA takedown to have bitcointalk remove this thread for copyright violations in 24 hours if the complete corresponding source code for all the distributed firmware binaries is not uploaded by then. I am a one of a number of cgminer copyright holders.I wasn't aware of the GPL license, so I did some investigation last days. After reading the GPL licenses I can conclude that stangerm2 is right. So that means I do have to provide the modified sources as most of the current modifications are now build on top of a linked module in cgminer.
There are some consequences in releasing the source though:
- As far as I know, Bitmain is free to use these improvements in their current and their new products they will sell. I do hope they compensate these free goodies with a multi algorithm D3 firmware one day
- There will probably appear modified firmware binaries which can cause damaging your miners if the maker doesn't know what he's doing...
- I had plans to buy a S9 as there are a lot of requests and make a modified S9 version, but I might consider not to jump on that boat for now. (let's first see what will happen with the D3)
Legit alternatives instead of releasing the sourcecode
- I stop this project and take the binaries offline. I don't like this option, as the whole idea is to help improve the situations for the D3 owners.
- Temporary I take the binaries offline and I will write something from scratch / not linked to the sources of cgminer. This will take away the consequences, but a lot of time and effort (at least a month or two) will be put into something that will probably not lead to any improvements for you guys.
My proposal
- Although these consequences I will release source of a stable version (non BETA) that allow others to investigate the voltage / fan mods / fault check improvements I did. (devfee related code will be removed from the source). This allow others to look into the changes I did to make a binary for themselves without devfee.
BETA functionality will be left out of the source right now since it's not yet stable and will create dangerous situations when used in a wrong way. I might have to restrict the use of a BETA versions to a closed group instead of providing a public link to the BETA versions.
Happy mining
Ciao Blissz
Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Still waiting for a response, btw.
What's the word on making the GPL3 source code available for review, Blissz?
To add some encouragement to getting this released, I'll be issuing a DMCA takedown to have bitcointalk remove this thread for copyright violations in 24 hours if the complete corresponding source code to the distributed firmware binaries is not uploaded by then. I am a one of a number of cgminer copyright holders.What's the word on making the GPL3 source code available for review, Blissz?
Re: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
According to the NYA, bit 4 was intended to be a signal for Segwit2x, and when btc1 is queried for the required softforks via GBT, btc1 has included segwit2x since bit 4 was triggered. Bit 4 is also supposed to be BIP91, so bit 4 is ambiguous. /NYA/ is unambiguous, but non-binding.
In the btc1 code the HF codepath was activated by bit 1, bit 4 was used only for BIP91.It's worth mentioning that Segwit2x can only exist if it has a majority of the hashrate. If your definition of Bitcoin is the post-fork chain with the most hashrate, then Segwit2x will either be Bitcoin or it won't exist. It's only if your definition of Bitcoin is Bitcoin Core that Segwit2x can be an altcoin.
Segwit2x has wipeout protection for full nodes(but not SPV wallets) so technically it can be a minority fork.Someone is feeding hackers all of the bugs that were fixed in Bitcoin Core since version 0.11.2 (or whatever version Unlimited forked from). I'm guessing they slam the BU nodes with a "new" exploit monthly, to keep pace with the news cycle and have "BU HAXXED OMFG" in the headlines once per month.
Not that big of a deal. BU is not the greatest code because it doesn't have enough devs. Core is a good team doing bad work for some financial saboteurs... Choose your posion.
This doesn't look to be the case, it would appear all the crashes so far have been due to a single very buggy feature(thin/xthin blocks) that was written by BU devs, it was never present in Core.Not that big of a deal. BU is not the greatest code because it doesn't have enough devs. Core is a good team doing bad work for some financial saboteurs... Choose your posion.
Obvious scam is obvious, take a look at their checkout page address generation code for proof.
They don't even bother to generate unique payment addresses for orders like any legitimate business would do, they just randomly select an address to show the user from a preloaded list in javascript. They wouldn't even be able to see who paid for an order since it's all done client side in javascript.
Code:
if($('body').is('.page-template-page-payment')){var bitcoinWallets=["1Ko6n7hC9aiHqbTDnSemfzAkrLUfh7i84N","19hgd15L8ZKWGtngEAXmiu5hVSr4wwSD1R","178PUWErgp8VoSksLjxpLjC3Na3hXxTSvN","1BCsw2CCjcVZPdyq2wtP32fZFDYWjoC61a","1LKoxHY8wTjF7DF4eYCpMkDXGY3PbUrBcK","16CKomZNtmVYF3yPQeQgwio34Wt8WSEn2d","1GtndhBkwjrPVz9EYMJdSjc3Pp81Q3zNef","14Z4tDkR9ru7b69miBFwNC5w9wphpd9NXD","16gWvK3MkZvwy8o79R4t3TX5dXivU3Admb","14D5P69iXdKJeav4icao6Sw2FioqLq9avC","1ELpEqXCfUjRSJdBQKP4s8hNApjb7k1qL","13M5Di8P7Sc5DxFLM8Pz1eZ8hDxDKGPshb","1PAXWWFMRafGs2WMZ5AcEME7kApRsozQPa","1FcWZVvDTeiToMFnhehgw7C69cVvTbQJPu","1MUAD2hFU4hsYXoKxFAh9AhcqpNJiSnR6C","1NuwmBykB43DyYY5jZU2fiXu56Q9Jb3tjD","16LLqGPqwdAJcirrv4UJQPb5qK7jNcLqVJ","1AAB9CAQuQU5e3Wz37oQiLkbZ9Xshjrm1v","1L4zAZi8CNX2btawG3UKcttGDJhchN23Sn","1GktTMe3unzFS6hZfB6KmgBQHhrT5TA5iA","1129gZCGxtfTMHRn7SDLTQutVh9aPg2RDv","1B7DMB17p44LHF929BwPJw5H7ehc1AGTHw","161WK4aHjV6HzWJoqHgT6519yjMBKavSVJ","1KNHdTqK5XJWW8Dr28Pg3Bb5nGw4pvpnZ2","1HFiRCXQTfXRPyQbW5bpnphhEBgojGVttu","15Ft51RkGo9PdTfLXTgMvBNwswGZWv1UX2","19LR319KU7V4AwtM63pF9jouKsgPmTJxzV","1DNL8kVX2N3et7KUGbfxkc6FfUShzgrKN3","1NFXDEAJU1wYyyqzRXN3PQzcHaE9wWLsS1","14QZswbiWwozfvdNhFgk3bCPXc6m3Pq8zW","1P4euAuKZN5nRrXpp93f9CN8FjFvmp3J5p","163aojhaLBnJDCXJB2eqxSuJvzyzF918pS","1P9CDaiy62BU9hYStfp8hVHf2T1FvcLhWe","1HgCT6x4Nkfr2o9QjM19PxwfqBf8gnZHXU","1E7Din341RW6YcwjCX63PJbCAZG14MYDNh","1NHJ8o9v25QjKJg7vbRXddwtuqugUJyegx","14pVNgERSXFjbntmhC1ADUpMxnwNALrNui","1FyfzHgGbbxAGNmVP729v117Z8kCkesucb","1AR9r53ZwPbXqWuRrvGR3cNs8TRgG3vUSf","1AFf58qECuANvkZYQEK2uhAGnGPtUq4mZn","16Pnb7Qd1pGHyaTkdQGM7F29ZjhVDAwgNb","1rFUrHCj3CL1R5u89porsRKRyfLoPHwor","1GiiDV2fhHV6WG6CXKdKifvZUYAnjsVvgA","1BXRydrc4pp2v7vz1MHUTHLqqYjCS8LD1R","1C3ht3MMU6QV39dtRZwNH3o35aSdch8kSG","1EHosqS4F7iGmiVRgToMtZ5v7P46joGgad","1EAJrB6A972tkdCGqjwjwMoHSrxqi45dZ1","1SGdw5SiVzjLKZXPJnChqUC1fE4RYCxq8","1HTSVsAKBq5Qrjqy1R9CpCsscb9voy9yg","1FpfqpYdUfL6XB32Y7Hn9MmDmuAcAdfQ2S","15qQNge3NX6sAnfeQrbZpP9bESFK2Lrd65","1PYBhQYEak7RhcFb6wi56GRLEqsWWcksVw","16yu6e3QuebSjafWHnaGKucQeVjm7GFAUr","1Q8ftB546ZSHJGHgJZztMDtbRyPSS9h5da","1jeYgs4mURB1cUY5m5MZmoyC2e7vucuAf","15tJS9js5S1XyZjeodiHh2oEZu5BzLC6qS","1HEQrjj3jSaF2fFVYY8YwaDN6fSuWrvaB3","1LDvGJZd8WSuxV4hei8xcD4xteWrA3gbj6","1GgxKViZqPZtSeZpRQz24W18qCwNiP8T3v","13mP5pE5Ughgi9YfAvtjUzp9oZPVEC3FQX","12gEfV1MCqyEGN4DMddV1PFxFptgs9fSwY","1DXND9p6hbsGuL8EYYRMeb158oq3aDTuNe","1HECJFxkWRVXwyW1TpRrsVJapr3Yb4ptrZ","19vAxeMfrJhaEjyYE9wYsqgEtgRVu8Cx86","19if1aGdeQXsiEKfvpTMEkFJ332Bm1ENNL","1N5ojSmpVkafMuNhJst2NEm2zibhVvNHjB"];var litecoinWallets=["LZEMh4rtQYfswNK8uV4EziBDgFEJsXzRcm","LeHXRJ8XHTCQnxyW3jejRZeXWaDLisszfm","Lf1p1Mbefe8knzpjB2ehfMX124DfWsmXAi","LgEa7U6ciXrmicUp1XH4tc1MoZxC6EivYE","LP5yqVnvi2nVCLCixC7LRdv55i1VcmExvx","LKp9sRjZWuyhhM9i1HmgZPNWfPMh4SQZ5q","LKdNBVEJaTnGtzBaHetGPogrv4BqC6Gmwi","LXJcPA9ZqDLDFL3x9rewbmmUiHKvAYhH2V","Lb9x2ZfDeVagsoTPA1k7yLcd8W5pVbQii4","LZrQC7Ti8XRUiAk7iCyDg3skqAjCcFq7pC","Lhv4bBHSdZJRHyvs3dnNee9PKow7zjkD3d","LcaChm3SxvrG7rVS7xThSv8MrYY1CYwD4b","LbG7qCUvpjCzHXe2ZYFctbiYzjGEjar9ja","LPzhfJsYxv28dKQ1nYT9BG2JEsYdXfPtQv","LWPzJu5mAZgyB9e4W4S92w4wrYE7r6QaMS"]
function getRandomInt(min,max){return Math.floor(Math.random()*(max-min+1))+min;}
var bitcoinCount=localStorage.getItem('on_load_counter_bitcoin');if(bitcoinCount===null||bitcoinCount>65){bitcoinCount=0;}
$('.bitcoin-method span').html(bitcoinWallets[getRandomInt(0,65)]);bitcoinCount++;localStorage.setItem("on_load_counter_bitcoin",bitcoinCount);var litecoinCount=localStorage.getItem('on_load_counter_litecoin');if(litecoinCount===null||litecoinCount>14){litecoinCount=0;}
$('.litecoin-method span').html(litecoinWallets[getRandomInt(0,14)]);litecoinCount++;localStorage.setItem("on_load_counter_litecoin",litecoinCount);
function getRandomInt(min,max){return Math.floor(Math.random()*(max-min+1))+min;}
var bitcoinCount=localStorage.getItem('on_load_counter_bitcoin');if(bitcoinCount===null||bitcoinCount>65){bitcoinCount=0;}
$('.bitcoin-method span').html(bitcoinWallets[getRandomInt(0,65)]);bitcoinCount++;localStorage.setItem("on_load_counter_bitcoin",bitcoinCount);var litecoinCount=localStorage.getItem('on_load_counter_litecoin');if(litecoinCount===null||litecoinCount>14){litecoinCount=0;}
$('.litecoin-method span').html(litecoinWallets[getRandomInt(0,14)]);litecoinCount++;localStorage.setItem("on_load_counter_litecoin",litecoinCount);
They don't even bother to generate unique payment addresses for orders like any legitimate business would do, they just randomly select an address to show the user from a preloaded list in javascript. They wouldn't even be able to see who paid for an order since it's all done client side in javascript.
The 75% he is referring to is if BIP100 was ALREADY activated.
I don't see any activation threshold, best I can tell is that it's effectively 75% since there isn't anything else.The problem lies on getting a 75% consensus from the miners
75% among just miners is way too low a threshold, you need strong economic support as well which is unlikely to happen at this point(SegWit is really the only proposal at this time with a decent level of support from the economy), and even then you probably want 90% or higher miner support in addition to a very long lead time(6-12 months) for any HF.Maybe because Bitcoin Core 0.12 code is known by a very large number of people, so it can have a very good peer review.
Core 0.12 should not be used for mining, there are known DoS vectors that were patched later on.Keep in mind this isn't the original BIP100 proposal, this is hacked up version that's IMO significantly more risky.
Re: [PPLNS 0.5%] RigPool.com -PPLNS Bitcoin BTC Mining Pool (FIRST BLOCK SOLVED)
It's been a while since we hit a block but still chipping away.
The pool's coin daemon has been updated to 0.13.2
FYI you also need to update your pool's stratum server to support segwit. I checked using my decoder tool and it isn't showing as supported.The pool's coin daemon has been updated to 0.13.2
Re: Post your SegWit questions here - open discussion - big week for Bitcoin!
I agree that Bitcoin core has had a lower rate of bugs per lines of code than industry average, but when you increase complexity, and particularly when you increase the number of lines of code, you create defects. It's a hard and fast rule of the software industry, ask anyone (except a Java programmer).
In reality SegWit is cleaning up a lot of technical debt with the transaction format and it's simplifying things for wallets that use it. SegWit simplifies transaction handling complexity by fixing the malleability issue fundamentally, this should reduce defects in all wallets that use it.
I find it very hard to believe that implementing Segwit support in existing software will be easier than a 2MB hard fork, please site a source for this.
SegWit(or a similar transaction format fix) is effectively a prerequisite for any block size increase hard fork due to the sighash issue. BIP109(Classic) ended up using the same limiter proposed in BIP101 which has issues(it makes testing of some codepaths more difficult for one), funny enough even Gavin argued against the approach ultimately used in BIP109, they used it anyways after realizing some pools used transactions over 100,000 bytes for payouts. SegWit is also backwards compatible so unlike a hard fork existing software doesn't have to rush code out without a chance to properly test. Rushing and skipping testing/code review is something that certainly increases defects in the software industry.
Re: Post your SegWit questions here - open discussion - big week for Bitcoin!
I'm sure that you are a solid developer since you run a mining pool. Are you 100% confident that changing 4743 lines of code deep in the Bitcoin codebase won't have any issues? And what about wallet and 3rd party software? When you add it all up, we're looking at tens of thousands of lines of code changes, which guarantees roughly 150-500 bugs (industry average) in all of this software, of which 2-5 are potentially catastrophic...
A hard fork to 2MB would involve one line of code change and some late-night sweating and swearing for a week
Bitcoin Core does not follow normal industry standards in regards to defect rates, this is due to a huge emphasis on code review and testing by domain experts in cryptography and secure programming(a large amount of code written for SegWit is testing code), and when it comes to consensus critical code like SegWit extra care is taken during testing to prevent defects beyond what is typically done in areas of the codebase that aren't consensus critical. SegWit in Bitcoin Core is some of the most thoroughly tested code in the Bitcoin industry and is unlikely to have any bugs that would cause serious issues.A hard fork to 2MB would involve one line of code change and some late-night sweating and swearing for a week
When it comes to support for wallets most rely on well reviewed 3rd party libraries that are ready to support SegWit. For some wallets like hardware wallets SegWit helps a lot since it fixes issues with the transaction format.
Interestingly enough a lot of the code that was written for SegWit would also have needed to be written in the event of a hard fork, for example the preferential peering code written for SegWit would also be needed for any hard fork. Due to the difficulty in activation coordination and other issues such as the sigop/sighash scaling issue there's no such thing as a simple 2MB hard fork.
Actually the spammer simply increases her fees. One must keep in mind that the spammer relies the fact that only a very small portion of the spam transactions will actually get mined regardless of the fees because of the fixed blocksize. A dynamic blocksize with a proper fee structure can be a very effective deterrent against this type of spam attack because by threatening to mine the spam it imposes a very significant risk to the spammer.
The spammer increasing their fees just causes legitimate transaction fees to increase since wallets use dynamic fee calculators, this prices the spammer out of the blocks since transaction fees are relatively small for the legitimate users but large for the spammer(since they are trying to buy a lot of block space). Without a cap fees would likely be too low to price the spammer out of the blocks.