Bitcoin Forum
May 05, 2021, 10:08:13 PM *
News: Latest Bitcoin Core release: 0.21.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 [598] 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 ... 1319 »
  Print  
Author Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000  (Read 2167791 times)
Irontiga
Hero Member
*****
Offline Offline

Activity: 588
Merit: 500


View Profile
September 26, 2014, 09:34:48 PM
 #11941



well, for one, the burstpool.ddns.net is port 8124, so you have to use burstpool.ddns.net:8124

The other pool I can't help you, but that should get you working on burstpool.ddns.net.



Trust me I already tried 8124 port , I wrote it above where I specify the issue
EDIT: I can run JAVA miner on port 80 at DDNS pool

You must use dcct or uray miner on this pool
1620252493
Hero Member
*
Offline Offline

Posts: 1620252493

View Profile Personal Message (Offline)

Ignore
1620252493
Reply with quote  #2

1620252493
Report to moderator
1620252493
Hero Member
*
Offline Offline

Posts: 1620252493

View Profile Personal Message (Offline)

Ignore
1620252493
Reply with quote  #2

1620252493
Report to moderator
1620252493
Hero Member
*
Offline Offline

Posts: 1620252493

View Profile Personal Message (Offline)

Ignore
1620252493
Reply with quote  #2

1620252493
Report to moderator
The trust scores you see are subjective; they will change depending on who you have in your trust list.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
bigeliphant
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
September 26, 2014, 10:05:02 PM
Last edit: September 26, 2014, 10:30:34 PM by bigeliphant
 #11942

If my hdd is 1tb but it show up as 931gb, does that mean i shouldn't go over 931gb creating plots?

add: must be, it's that macintosh is different, it's 1tb in bytes.
uray
Hero Member
*****
Offline Offline

Activity: 1274
Merit: 504



View Profile
September 26, 2014, 10:07:44 PM
 #11943

is it possible see the deadline that found the block in the block expoler?

You can infer it with reasonable accuracy from the delay since the reporting of the previous block.



see that small text below tx amount
Round Time ...
its the deadline for that block

.
.ApeSwap.
The next-gen AMM,
Staking and Farming
Protocol on BSC
           ▄██▄
          ██████
          ██████
          ██████ ▄▄███▄
          █████
███▀ ▀▀█
    ▄█████████████▌    ▀█
   ██▀  ▀█████████▄     ▀█
  ██      █████████▄
 ▄█▀       █████████▄
▀▀          ▀█████████▄
              ▀█████████▄
                ▀█████████▄
                   ▀▀▀▀▀▀██
██████
██
██
██
██
██
██
██
██
██
██
██
██████
Stake now
for over 900% APR!
██████
██
██
██
██
██
██
██
██
██
██
██
██████
Brandon1000
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
September 26, 2014, 10:48:21 PM
 #11944

I use POC_Pool miner and keep getting this error spuraticly and not sure why. Any help?

[INFO] [09/25/2014 15:16:55.970] [default-akka.actor.default-dispatcher-2] [akka://default/user/$a/$c] Message [pocminer_pool.Miner$msgSendResults] from Actor[akka://default/deadLetters] to Actor[akka://default/user/$a/$c#-1365268779] was not delivered. [1] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.

my bat file:

C:\Windows\SysWOW64\java -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://178.62.39.204:8121
planeswalker
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
September 26, 2014, 11:15:18 PM
 #11945

I also have the same problem.
Windows 8.1 64Bits

@Uray and @Blago:

Guys obviously I have some regional issue with connecting the remote IP using R3/R4 Uray's miners such an issue I have with the Blago's miner:

My settings at R4 miner in the conf file are:

 {
    "poolUrl" : "burstpool.ddns.net",
    "submissionMaxDelay" : 30,
    "submissionMaxRetry" : 3,
    "socketTimeout" : 60,
    "maxBufferSizeMB" : 2048,
    "plots" :
    [
       "D:\\BURST\\gpuPlotGenerator-bin-win-x86-2.1.1\\plots"
   ]
 }

It doesn't matter if I set buffersize 64 / 2048 / 4096.. Also doesn't matter if I set port (8124 for DDNS pool) or not (80 port). I tried with firewall absolutely OFF- same situation.
I have different account on other PCs with different IPs and location , the accounts are for both Uray's pools - same issue.
Let me show you some screenshots:

https://i.imgur.com/3AEn7w2.jpg
https://i.imgur.com/yWGaBDF.jpg

I'm still using JAVA miner without any issue , but I have to start different miner for every single HDD ploted...


well, for one, the burstpool.ddns.net is port 8124, so you have to use burstpool.ddns.net:8124

The other pool I can't help you, but that should get you working on burstpool.ddns.net.

I had this issue but changing the drive letter to lowercase fixed it.  I guess tolower(); wasn't used?
go6ooo1212
Legendary
*
Offline Offline

Activity: 1512
Merit: 1000


quarkchain.io


View Profile
September 27, 2014, 12:03:49 AM
 #11946

I had this issue but changing the drive letter to lowercase fixed it.  I guess tolower(); wasn't used?

It doesn't take any change to me
agran
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


View Profile
September 27, 2014, 01:16:02 AM
 #11947

https://bter.com/voting#BURST

Pleace voite!

Already - 2,317 votes and 17 place.

QORA | 2ND GEN | NEW SOURCE CODE | QTz6fSV2VNc2wjwwsw57kwQzgQhmGw5idQ
BChydro
Hero Member
*****
Offline Offline

Activity: 1399
Merit: 505



View Profile
September 27, 2014, 01:41:01 AM
 #11948

Does anyone know how much BTR you need to get 2 votes per hour on bter.com?

.
.ApeSwap.
The next-gen AMM,
Staking and Farming
Protocol on BSC
           ▄██▄
          ██████
          ██████
          ██████ ▄▄███▄
          █████
███▀ ▀▀█
    ▄█████████████▌    ▀█
   ██▀  ▀█████████▄     ▀█
  ██      █████████▄
 ▄█▀       █████████▄
▀▀          ▀█████████▄
              ▀█████████▄
                ▀█████████▄
                   ▀▀▀▀▀▀██
██████
██
██
██
██
██
██
██
██
██
██
██
██████
Stake now
for over 900% APR!
██████
██
██
██
██
██
██
██
██
██
██
██
██████
Blago
Sr. Member
****
Offline Offline

Activity: 416
Merit: 250



View Profile
September 27, 2014, 02:19:42 AM
Last edit: September 27, 2014, 02:34:13 AM by Blago
 #11949

I had this issue but changing the drive letter to lowercase fixed it.  I guess tolower(); wasn't used?

It doesn't take any change to me

I can not find the problem, because the miner is working fine for me with a pool:

Code:
miner.exe pool burstpool.ddns.net 8124 C:\pocminer_v1-burst\plots\ D:\pocminer_v1-burst\plots\ E:\pocminer_v1-burst\plots\ G:\pocminer_v1-burst\plots\ H:\pocminer_v1-burst\plots\ F:\plots\

Note:
drive letter upper case.
No deadlines because i did not set reward assignment, but miner sent shares and get mining info from pool (trying port 80 and 8124)



Relax, I’m russian!...
BURST-B2LU-SGCZ-NYVS-HZEPK
SpeedDemon13
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile WWW
September 27, 2014, 02:22:39 AM
 #11950

Native C++ Miner Update 1.1 R4

binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64

  • capable to read large stagger plot, with manual limit option on memory usage
  • Fix thread race condition, which reported to less nonce read
  • add option of buffer size (MB) in mining.conf to limit memory usage

and also, github automatically give the project website : http://uraymeiviar.github.io/burst-miner/

So, is this only for pool mining at your pool? Or can this solo mine also?

CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911
mafostedu
Full Member
***
Offline Offline

Activity: 171
Merit: 100


View Profile
September 27, 2014, 03:58:04 AM
 #11951

ok, i will make optimization, but after we dont have any critical issue first, i want to make this miner can read any weird and funky plot first

Can you also implement log file generation so that we can check when the miner is crashed & find out the possible reason behind  that crash ?
jamoes
Member
**
Offline Offline

Activity: 89
Merit: 10


View Profile
September 27, 2014, 04:03:25 AM
 #11952

I just noticed that http://coinmarketcap.com is now properly showing the market cap for burst. Burst is ranked exactly 100 right now.
burstcoin
Sr. Member
****
Offline Offline

Activity: 280
Merit: 250


View Profile
September 27, 2014, 04:28:55 AM
 #11953

New client Burst 1.1.3

download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.

Update is required.

Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.

After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.

This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.

BURST-QHCJ-9HB5-PTGC-5Q8J9
cyberspacemonkey
Legendary
*
Offline Offline

Activity: 1288
Merit: 1002


View Profile
September 27, 2014, 04:45:30 AM
 #11954

New client Burst 1.1.3

download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.

Update is required.

Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.

After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.

This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.

Do we need to re-download the blockchain? or the one I have from the old wallet will work fine?
burstcoin
Sr. Member
****
Offline Offline

Activity: 280
Merit: 250


View Profile
September 27, 2014, 04:47:30 AM
 #11955

New client Burst 1.1.3

download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.

Update is required.

Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.

After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.

This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.

Do we need to re-download the blockchain? or the one I have from the old wallet will work fine?

Old blockchain is fine, just move the folder over.

BURST-QHCJ-9HB5-PTGC-5Q8J9
DrTrouble
Member
**
Offline Offline

Activity: 111
Merit: 10


View Profile
September 27, 2014, 05:13:01 AM
 #11956

Am I correct in saying that a passphrases.txt is not needed in a folder when pool mining?  In particular, pool mining on http://burstpool.ddns.net/ with 'Burst Mining System'? 

That being said, what is the best way to track that my shares are properly getting submitted to the pool and such? 

I like BURST and I have several different miners hitting it.  But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out.  There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!

Thanks all!

What is this "Bitcoin" of which you speak???
Irontiga
Hero Member
*****
Offline Offline

Activity: 588
Merit: 500


View Profile
September 27, 2014, 05:21:06 AM
 #11957

Am I correct in saying that a passphrases.txt is not needed in a folder when pool mining?  In particular, pool mining on http://burstpool.ddns.net/ with 'Burst Mining System'? 

That being said, what is the best way to track that my shares are properly getting submitted to the pool and such? 

I like BURST and I have several different miners hitting it.  But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out.  There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!

Thanks all!

No, remove passphrase for pool mining.
Irontiga
Hero Member
*****
Offline Offline

Activity: 588
Merit: 500


View Profile
September 27, 2014, 05:25:59 AM
 #11958

Hello, and attention all miners of burstpool.ddns.net

Please remember that those who were mining before this announcement https://burstforum.com/index.php?threads/the-big-announcement.149/ get first choice for shares. In a few days we will be making them available to all, so please send your 1k (or less) burst to BURST-T7BK-USTG-KVKC-D2RDL and you will be sent 10 shares in the pool.

NOTE: Max 10 shares per person mining on the pool pre-announcement. Also, currently only available to those who were mining on the pool pre-announcement. If you are interested and weren't mining on the pool pre-announcement, place a bid order and wish that someone who was mining pre-announcement sells to you, or just wait till we make shares public.

--Irotniga
DrTrouble
Member
**
Offline Offline

Activity: 111
Merit: 10


View Profile
September 27, 2014, 05:30:21 AM
 #11959

Hello, and attention all miners of burstpool.ddns.net

Please remember that those who were mining before this announcement https://burstforum.com/index.php?threads/the-big-announcement.149/ get first choice for shares. In a few days we will be making them available to all, so please send your 1k (or less) burst to BURST-T7BK-USTG-KVKC-D2RDL and you will be sent 10 shares in the pool.

NOTE: Max 10 shares per person mining on the pool pre-announcement. Also, currently only available to those who were mining on the pool pre-announcement. If you are interested and weren't mining on the pool pre-announcement, place a bid order and wish that someone who was mining pre-announcement sells to you, or just wait till we make shares public.

--Irotniga

I got in on this earlier today.  Yea buddy!

What is this "Bitcoin" of which you speak???
DrTrouble
Member
**
Offline Offline

Activity: 111
Merit: 10


View Profile
September 27, 2014, 05:31:07 AM
 #11960

Am I correct in saying that a passphrases.txt is not needed in a folder when pool mining?  In particular, pool mining on http://burstpool.ddns.net/ with 'Burst Mining System'? 

That being said, what is the best way to track that my shares are properly getting submitted to the pool and such? 

I like BURST and I have several different miners hitting it.  But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out.  There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!

Thanks all!

No, remove passphrase for pool mining.

Ok, that's what I thought/said above.  Thank you!

What is this "Bitcoin" of which you speak???
Pages: « 1 ... 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 [598] 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 ... 1319 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!