Baikal Giant X10

[rogerthat55]

Anyone ordered directly from Baikal before? This is what they keep asking me about:

A.If paid from personal bank account.
Then provide 1)name of account owner, 2)remitter identification card
 
B.If paid from company bank account.
then provide 1)name of company, 2)registration address of company, 3)business license.

I'm in the U.S. and I can pay either way, from personal bank account or company bank account. Is a remitter identification card a driver's license? What about the business license? I have a DBA for my business, which just says I am doing business as an alternate name (and allows me to open a business bank account).

[1713546747]

1713546747

[GunsN]

Anyone ordered directly from Baikal before? This is what they keep asking me about:

A.If paid from personal bank account.
Then provide 1)name of account owner, 2)remitter identification card
 
B.If paid from company bank account.
then provide 1)name of company, 2)registration address of company, 3)business license.

I'm in the U.S. and I can pay either way, from personal bank account or company bank account. Is a remitter identification card a driver's license? What about the business license? I have a DBA for my business, which just says I am doing business as an alternate name (and allows me to open a business bank account).

pay just from personal bank account.

[mo_the_miner]

Hi to All of you .

someone any news regarding the 2 extra algorithms ?

All i read is : will be added soon .. as from November 2017 

[dirtmonster]

I asked a dew days ago and baikal said to me 4000 USD for x10, someone knows why they reduce the price??

Simple, cause they aren't selling fast enough. They lower price little by little to get the suckers that want to pay more first before getting the rest of the buyers. That's why they were selling at first for like $7000.

How they work:
Get suckers that wants to pay $7000, then when there's no more suckers, lower to $6000, and when no more suckers, lower again, rinse and repeat until stock is gone.

In other words, to maximize their profits since they aren't as big as Bitmain to be pumping out toasters non-stop.

So for more me, I woudn't pay anywhere close to $2000.

Remember, they were originally selling for $1188 so they had to make profits. Once they realized third party sellers were selling for a lot more, their price jumped.

Whoah senior member going bad on Baikal! Price is $2600 now, would you go for that?  What do you go for since you've seen alot?

[wolf_miner]

Hi, what is the actual price of X10 directly form Baikal?

Cheers W_M

[ruplikminer]

Hi, what is the actual price of X10 directly form Baikal?

Cheers W_M

2699 usd MOQ 2 units

[Selector79]

Hi to All of you .

someone any news regarding the 2 extra algorithms ?

All i read is : will be added soon .. as from November 2017 

Soon is November 2019

[fawasme]

For anyone having troubles with their Giant X10, could you try logging into it (default user:pass is baikal:baikal) and running this command:

Code:

lsusb | grep 0483

This command will list the USB devices attached to the OrangePi and then filter those results to only show lines with "0483" (STMicroelectronics' USB vendor ID). The expected result is this (where things should be working properly):

Code:

Bus 007 Device 003: ID 0483:5740 STMicroelectronics STM32F407

But if you get this:

Code:

Bus 007 Device 002: ID 0483:df11 STMicroelectronics STM Device in DFU Mode

Then the STM32 microcontroller may need to be reset (it is stuck in firmware download mode). If this is the case, issue these two commands:

Code:

echo 0 > /sys/class/gpio_sw/PA10/data
echo 1 > /sys/class/gpio_sw/PA10/data

The first command sets the PA10 pin to 0 (off) on the OrangePi, which is connected to the STM32's reset pin, which in turn holds it in a reset state (it needs to be at 0v to reset). The second command de-asserts (sets to 1 in this case) the reset pin allowing the STM32 to begin normal operations. These steps fixed the issue with a Giant X10 I looked at. These commands may need to be run again after reboot, so you may want to write a script in your favorite language to do this at boot or to do a periodic check.

If you get "permission denied" (or something like that, I don't remember the exact message ATM) when trying those commands, try this first:

Code:

su

(then type "baikal" again for the password to elevate your terminal to root level)
Or simply log in as root:baikal instead.

Please do a quick Google search of these commands first to know that they're actually doing what I've explained above. You should default to not trusting random internet stranger's instructions if you're not familiar with what you're doing. Hopefully this helps someone solve their miner issues. Please post if you tried these steps and it solved the issue for you so I know if this is a common problem or if I'm the only one who had trouble with it. Happy mining!

[/size]

Thank you so much for this!  It resurrected 2 of my miners.

1)On the Giant X10 Has anyone experienced problems with the Scrypta Page under MINER Settings not loading?. I dont get it to work anymore, tried to restore backups over and over with no result.

2)Has anyone tried through terminal to disable the led blinking lights during nightime? is it possible?.

3) XVG vs. Digibyte-Multialgo on Mininpoolhub? what are you guys making more profit from?

Thanks people!!

[Dlikrot]

Have anyone tried to get x13 to work on the x10? Would be sweet to get working...

[CNoteFan]

For anyone having troubles with their Giant X10, could you try logging into it (default user:pass is baikal:baikal) and running this command:

Code:

lsusb | grep 0483

This command will list the USB devices attached to the OrangePi and then filter those results to only show lines with "0483" (STMicroelectronics' USB vendor ID). The expected result is this (where things should be working properly):

Code:

Bus 007 Device 003: ID 0483:5740 STMicroelectronics STM32F407

But if you get this:

Code:

Bus 007 Device 002: ID 0483:df11 STMicroelectronics STM Device in DFU Mode

Then the STM32 microcontroller may need to be reset (it is stuck in firmware download mode). If this is the case, issue these two commands:

Code:

echo 0 > /sys/class/gpio_sw/PA10/data
echo 1 > /sys/class/gpio_sw/PA10/data

The first command sets the PA10 pin to 0 (off) on the OrangePi, which is connected to the STM32's reset pin, which in turn holds it in a reset state (it needs to be at 0v to reset). The second command de-asserts (sets to 1 in this case) the reset pin allowing the STM32 to begin normal operations. These steps fixed the issue with a Giant X10 I looked at. These commands may need to be run again after reboot, so you may want to write a script in your favorite language to do this at boot or to do a periodic check.

If you get "permission denied" (or something like that, I don't remember the exact message ATM) when trying those commands, try this first:

Code:

su

(then type "baikal" again for the password to elevate your terminal to root level)
Or simply log in as root:baikal instead.

Please do a quick Google search of these commands first to know that they're actually doing what I've explained above. You should default to not trusting random internet stranger's instructions if you're not familiar with what you're doing. Hopefully this helps someone solve their miner issues. Please post if you tried these steps and it solved the issue for you so I know if this is a common problem or if I'm the only one who had trouble with it. Happy mining!

[/size]

Thank you so much for this!  It resurrected 2 of my miners.

1)On the Giant X10 Has anyone experienced problems with the Scrypta Page under MINER Settings not loading?. I dont get it to work anymore, tried to restore backups over and over with no result.

2)Has anyone tried through terminal to disable the led blinking lights during nightime? is it possible?.

3) XVG vs. Digibyte-Multialgo on Mininpoolhub? what are you guys making more profit from?

Thanks people!!

If I recall correctly, to remedy this in the past, I've re-imaged the SD card.  There's a good chance the SD card itself is going bad.  I've found a few.

[pikachuy]

Whoah senior member going bad on Baikal! Price is $2600 now, would you go for that?  What do you go for since you've seen alot?

Lets say if you buy it for $2600 and say it makes about $10 a day after electricity (best to be conservative).

$2600 / $10 day = 260 days / 30days = about 8.6 months.

That's already at the end of 2018.

By the time you break even, they will most likely already/soon release a new updated miner and yours already outdated.


If you are fine with 8 months to break even, then that price will be great for you. For me 8 months is too long, I would rather just hold that $2600 value in BTC for 8 months and buy their future updated gear.

Who knows, by the end of the year BTC value might double so you can buy more gear.

[wolf_miner]

I asked for BAIKAL price because Asicminermarket offer X10, to their previous customers, at $2099 shipping included, so I have thinked that BAIKAL lowered its prices.

Cheers W_M

[Goool]

Whoah senior member going bad on Baikal! Price is $2600 now, would you go for that?  What do you go for since you've seen alot?

Lets say if you buy it for $2600 and say it makes about $10 a day after electricity (best to be conservative).

$2600 / $10 day = 260 days / 30days = about 8.6 months.

That's already at the end of 2018.

By the time you break even, they will most likely already/soon release a new updated miner and yours already outdated.


If you are fine with 8 months to break even, then that price will be great for you. For me 8 months is too long, I would rather just hold that $2600 value in BTC for 8 months and buy their future updated gear.

Who knows, by the end of the year BTC value might double so you can buy more gear.

You are in my mind !!
Better hold coins than buy BAIKAL... in early June is expected to sky rocket btc like the 2 previous years ... so 3 months of holding coins it sounds better than min 10 months of mining and if you still make $10 .... they have huge stock ....

[cryptonitro]

Hey friends

 /laugh .....

Nothing is excepted with cryptocurrency market .

No one as understand the worst ? i'm not smart but logic ... "2 algos updated soon" , close to 5 month old announce , and now price reduction ?!  their will be no new algo "soon" cause they can't debug  it  and dont have a good hashrate , if new algos were promising to profit,  the price of x10 never decrease like this !

Many x10 will be connected soon , profit will reduce in month to come ! and dont hope for new algo change this !

Have a nice day friends

 

[Selector79]

Hey friends

 /laugh .....

Nothing is excepted with cryptocurrency market .

No one as understand the worst ? i'm not smart but logic ... "2 algos updated soon" , close to 5 month old announce , and now price reduction ?!  their will be no new algo "soon" cause they can't debug  it  and dont have a good hashrate , if new algos were promising to profit,  the price of x10 never decrease like this !

Many x10 will be connected soon , profit will reduce in month to come ! and dont hope for new algo change this !

Have a nice day friends

 

I think you are right!


Do not buy Baikal X10.   You do not get your money back!

Better you buy some coins for this money than you have more chances to earn something!


Baikal can really not debug new algorithms! Ohterwise we would get new algorithms or Baikal never make a price lower!!! If they see a chance to make more money, they never reduce the price!!!!!!!

[henrylitee]

hi,

i just got Baikal, i was trying to configurate the pools and i dont know what i did but i cannot enter to baikal anymore, once i tope the ip ardes from baikal it takes a lot of time but i cannot enter to baikal options set up anymore,

what should i do

[craigh]

hi,

i just got Baikal, i was trying to configurate the pools and i dont know what i did but i cannot enter to baikal anymore, once i tope the ip ardes from baikal it takes a lot of time but i cannot enter to baikal options set up anymore,

what should i do

Switch it off and on again. 

If that doesn't work, re-image the SD card.

C.

[pikachuy]

Member CNoteFan found some interesting information at https://bitcointalk.org/index.php?topic=2790982.msg32982356#msg32982356

Looking at part of the deleted code:

Code:

switch (baikal->algorithm.type) {
    case ALGO_BLAKECOIN:        // blake256r8
    case ALGO_VANILLA:
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[64], 16);
            be32enc_vect((uint32_t *)&msg.data[42], (const uint32_t *)&msg.data[42], 4);
            *((uint32_t *)&msg.data[58]) = 0x00000080;
            *((uint32_t *)&msg.data[94]) = 0x01000000;
            *((uint32_t *)&msg.data[102]) = 0x80020000;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 80);
            be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
            msg.len = 90;
        }
        break;

    case ALGO_DECRED:           // blake256r14
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[128], 52);
            *((uint32_t *)&msg.data[94]) = 0x01000080UL;
            *((uint32_t *)&msg.data[98]) = 0x00000000UL;
            *((uint32_t *)&msg.data[102]) = 0xa0050000UL;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 180);
            msg.len = 190;
        }
        break;
    case ALGO_SIA:              // blake2b
        memcpy(&msg.data[10], work->data, 80);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
        msg.len = 90;
        break;

    case ALGO_LBRY:             // lbry-all
        memcpy(&msg.data[10], work->data, 112);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 27);
        msg.len = 122;
        break;

    case ALGO_PASCAL:           // lbry-sha
        memcpy(&msg.data[10], work->data, 200);
        msg.len = 210;
        break;

    case ALGO_X11:
    case ALGO_X11GOST:
    case ALGO_SKEINCOIN:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_GROESTL:
    case ALGO_SKEIN2:
    case ALGO_NIST:
    case ALGO_CRYPTONIGHT:
    case ALGO_CRYPTONIGHT_LITE:
    case ALGO_BLAKE:
    case ALGO_VELTOR:

It list blake256r8, VANILLA, blake256r14, blake2b, LBRY, PASCAL but blanks out the following:
    case ALGO_X11:
    case ALGO_X11GOST:
    case ALGO_SKEINCOIN:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_GROESTL:
    case ALGO_SKEIN2:
    case ALGO_NIST:
    case ALGO_CRYPTONIGHT:
    case ALGO_CRYPTONIGHT_LITE:
    case ALGO_BLAKE:
    case ALGO_VELTOR:

So I am guessing that source code is for the Baikal Giant B. In other words, they already know their list of ALGO but keeping hush. As you can see the Baikal Giant N algo is on the list too. Guess that gives a more confident reason that the 2 missing algo is NIST and GROESTL and most likely mining themselves.

Now the question is, if they would of been able to not blank anything out and turn it into one super 15+ algo miner. Then again, they won't sell as much and would profit more by breaking it down into multiple miners. Just a theory, I could be all wrong...

[fawasme]

Member CNoteFan found some interesting information at https://bitcointalk.org/index.php?topic=2790982.msg32982356#msg32982356

Looking at part of the deleted code:

Code:

switch (baikal->algorithm.type) {
    case ALGO_BLAKECOIN:        // blake256r8
    case ALGO_VANILLA:
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[64], 16);
            be32enc_vect((uint32_t *)&msg.data[42], (const uint32_t *)&msg.data[42], 4);
            *((uint32_t *)&msg.data[58]) = 0x00000080;
            *((uint32_t *)&msg.data[94]) = 0x01000000;
            *((uint32_t *)&msg.data[102]) = 0x80020000;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 80);
            be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
            msg.len = 90;
        }
        break;

    case ALGO_DECRED:           // blake256r14
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[128], 52);
            *((uint32_t *)&msg.data[94]) = 0x01000080UL;
            *((uint32_t *)&msg.data[98]) = 0x00000000UL;
            *((uint32_t *)&msg.data[102]) = 0xa0050000UL;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 180);
            msg.len = 190;
        }
        break;
    case ALGO_SIA:              // blake2b
        memcpy(&msg.data[10], work->data, 80);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
        msg.len = 90;
        break;

    case ALGO_LBRY:             // lbry-all
        memcpy(&msg.data[10], work->data, 112);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 27);
        msg.len = 122;
        break;

    case ALGO_PASCAL:           // lbry-sha
        memcpy(&msg.data[10], work->data, 200);
        msg.len = 210;
        break;

    case ALGO_X11:
    case ALGO_X11GOST:
    case ALGO_SKEINCOIN:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_GROESTL:
    case ALGO_SKEIN2:
    case ALGO_NIST:
    case ALGO_CRYPTONIGHT:
    case ALGO_CRYPTONIGHT_LITE:
    case ALGO_BLAKE:
    case ALGO_VELTOR:

It list blake256r8, VANILLA, blake256r14, blake2b, LBRY, PASCAL but blanks out the following:
    case ALGO_X11:
    case ALGO_X11GOST:
    case ALGO_SKEINCOIN:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_GROESTL:
    case ALGO_SKEIN2:
    case ALGO_NIST:
    case ALGO_CRYPTONIGHT:
    case ALGO_CRYPTONIGHT_LITE:
    case ALGO_BLAKE:
    case ALGO_VELTOR:

So I am guessing that source code is for the Baikal Giant B. In other words, they already know their list of ALGO but keeping hush. As you can see the Baikal Giant N algo is on the list too. Guess that gives a more confident reason that the 2 missing algo is NIST and GROESTL and most likely mining themselves.

Now the question is, if they would of been able to not blank anything out and turn it into one super 15+ algo miner. Then again, they won't sell as much and would profit more by breaking it down into multiple miners. Just a theory, I could be all wrong...

Well, I think I will do whatever I can to modify my Baikal X10 to mine whatever I want so I can get back the 10k USD I spent on it, damn.....I getting nuts trying to recover my money!.

[bengaltiger]

Member CNoteFan found some interesting information at https://bitcointalk.org/index.php?topic=2790982.msg32982356#msg32982356

Looking at part of the deleted code:

Code:

switch (baikal->algorithm.type) {
    case ALGO_BLAKECOIN:        // blake256r8
    case ALGO_VANILLA:
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[64], 16);
            be32enc_vect((uint32_t *)&msg.data[42], (const uint32_t *)&msg.data[42], 4);
            *((uint32_t *)&msg.data[58]) = 0x00000080;
            *((uint32_t *)&msg.data[94]) = 0x01000000;
            *((uint32_t *)&msg.data[102]) = 0x80020000;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 80);
            be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
            msg.len = 90;
        }
        break;

    case ALGO_DECRED:           // blake256r14
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[128], 52);
            *((uint32_t *)&msg.data[94]) = 0x01000080UL;
            *((uint32_t *)&msg.data[98]) = 0x00000000UL;
            *((uint32_t *)&msg.data[102]) = 0xa0050000UL;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 180);
            msg.len = 190;
        }
        break;
    case ALGO_SIA:              // blake2b
        memcpy(&msg.data[10], work->data, 80);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
        msg.len = 90;
        break;

    case ALGO_LBRY:             // lbry-all
        memcpy(&msg.data[10], work->data, 112);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 27);
        msg.len = 122;
        break;

    case ALGO_PASCAL:           // lbry-sha
        memcpy(&msg.data[10], work->data, 200);
        msg.len = 210;
        break;

    case ALGO_X11:
    case ALGO_X11GOST:
    case ALGO_SKEINCOIN:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_GROESTL:
    case ALGO_SKEIN2:
    case ALGO_NIST:
    case ALGO_CRYPTONIGHT:
    case ALGO_CRYPTONIGHT_LITE:
    case ALGO_BLAKE:
    case ALGO_VELTOR:

It list blake256r8, VANILLA, blake256r14, blake2b, LBRY, PASCAL but blanks out the following:
    case ALGO_X11:
    case ALGO_X11GOST:
    case ALGO_SKEINCOIN:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_GROESTL:
    case ALGO_SKEIN2:
    case ALGO_NIST:
    case ALGO_CRYPTONIGHT:
    case ALGO_CRYPTONIGHT_LITE:
    case ALGO_BLAKE:
    case ALGO_VELTOR:

So I am guessing that source code is for the Baikal Giant B. In other words, they already know their list of ALGO but keeping hush. As you can see the Baikal Giant N algo is on the list too. Guess that gives a more confident reason that the 2 missing algo is NIST and GROESTL and most likely mining themselves.

Now the question is, if they would of been able to not blank anything out and turn it into one super 15+ algo miner. Then again, they won't sell as much and would profit more by breaking it down into multiple miners. Just a theory, I could be all wrong...

very interesting
but it doesnt matter whivh algo
the profit will go down rapidly btach 1,2 and3 baikals x10 are out
the only good thing is you can choose your favorite coin from these algos