Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - glongsword

Pages: [1] 2 3 4
1
Marketplace / Re: WTB 1000 PTS @ .019 BTC
« on: November 18, 2013, 07:52:12 am »
I've sent you a PM.  Do you want to buy 250?

2
BitShares PTS / Re: Confirmation time, is this normal?
« on: November 17, 2013, 07:35:23 pm »
The slow confirmation times appear to be the result of one or more miners having adopted a policy of refusing to include more than one transaction per block.  See here:

http://btsblock.com/chain/ProtoShares

Ypool (the largest pool) appears to be one the bad actors.  If you compare block numbers from their stats page to the blockchain explorer, it looks like all of ypool's blocks are only including 1 transaction at most.

Thus, everyone trying to send PTS through the network is having to wait until someone else (such as the beeeeer pool) find a block, at which point a bunch of transactions finally get included in a block.

Why would they refuse transactions?

I hadn't realized this was going on, but was noticing that most of my transactions took 2-4 blocks before getting confirmed, even though I paid the fees.  At least now I know why that was happening.

3
I get this message on make:

Quote
In file included from /usr/local/include/boost/atomic/detail/platform.hpp:22:0,
                 from /usr/local/include/boost/atomic/atomic.hpp:17,
                 from /usr/local/include/boost/atomic.hpp:12,
                 from /usr/local/include/boost/thread/pthread/once_atomic.hpp:20,
                 from /usr/local/include/boost/thread/once.hpp:20,
                 from /usr/local/include/boost/thread.hpp:17,
                 from /home/ubuntu/coyote_miner_update/fc/src/thread/thread_d.hpp:4,
                 from /home/ubuntu/coyote_miner_update/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp: In member function ‘void fc::thread_d::process_tasks()’:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for ‘__atomic_exchange’
         return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
                                                                                               ^
make[2]: *** [fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o] Error 1
make[1]: *** [fc/CMakeFiles/fc.dir/all] Error 2
make: *** [all] Error 2

I'm using Boost 1.55

Switched to Boost 1.54, compiles fine.

4
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 14, 2013, 05:20:18 pm »
when try to wget the coyote miner from

Code: [Select]
wget  https://the-iland.net/static/downloads/linux_coyote_miner.0.1.0.tar.gz
i get this message

Code: [Select]
Connecting to the-iland.net (the-iland.net)|64.90.183.137|:443... connected.
ERROR: cannot verify the-iland.net's certificate, issued by ‘/C=US/ST=Virginia/O=The iLand Nation/CN=the-iland.net/[email protected]’:
  Self-signed certificate encountered.
To connect to the-iland.net insecurely, use `--no-check-certificate'.

anybody wiht same issue before!?

Try this instead: wget  http://the-iland.net/static/downloads/linux_coyote_miner.0.1.0.tar.gz

5
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 14, 2013, 04:28:24 pm »
Is it possible to mine multiple pc with one wallet adress on this miner?

Yes, just specify the same address from that wallet on the different computers when calling coyote_miner

6
It looked like I was able to mine to the same computer over IP, but even though it was reporting a hashrate it was using 0% of the cpu, so I switched to each computer mining to their own wallet.

I'm seeing something worrisome, though.  A bunch of miners will simultaneously show that they calculated the exact same hash!  I imagine this implies there is a ton of duplicated effort.  I've seen this quite a few times.  Is there a way to get them to work on different problems?  If I connect them to the same wallet through IP, would that fix it?

7
Marketplace / [WTS] 2000 @ .009 BTC/PTS
« on: November 14, 2013, 01:03:22 am »
Largest offer for the lowest price!

No minimum PTS per order.

8
When I run it without arguments, it benchmarks.  But when I try to connect to localhost, it reports this:

Quote
./gw_miner localhost x y
/root/coyote_miner/bitcoin.cpp(88): Throw in function boost::property_tree::ptree bitcoin::detail::client::request(const string&)
Dynamic exception type: boost::exception_detail::clone_impl<bitcoin::exception>
std::exception::what: bitcoin::exception
[bitcoin::bitcoin_msg_*] = Response returned with status code 500


I installed boost 1.53 development and debug so that should include all the boost libraries.  Any ideas?

EDIT: stopping and starting bitcoind a few times and trying again resolves the issue.

Also, occasionally it will display hashes, but still say "ACCEPTED: 0."  Is this normal?

9
hey bytemaster any idea about this error?
http://bitsharestalk.org/index.php?topic=573.msg5661#msg5661

i found this random file on the net and put it in that directory and it seems to compile.

http://www.iis.ee.ethz.ch/~sha3/gmu_sha2/simvectors/md_helper.c.html

So maybe your repo is just missing that file?

git pull fixes that.

10

Make sure you pull the latest, it was missing in an earlier checkin.

If it's running correctly, should there be some text output?

11
I'm getting a different error:

Quote
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::get_current_thread_data()':
(.text+0x19d): undefined reference to `pthread_key_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::set_current_thread_data(boost::detail::thread_data_base*)':
(.text+0x1dd): undefined reference to `pthread_key_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::start_thread_noexcept()':
(.text+0x253): undefined reference to `pthread_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::start_thread_noexcept(boost::thread_attributes const&)':
(.text+0x2d2): undefined reference to `pthread_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::detach()':
(.text+0x61d): undefined reference to `pthread_detach'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::join_noexcept()':
(.text+0xfb2): undefined reference to `pthread_join'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::do_try_join_until_noexcept(timespec const&, bool&)':
(.text+0x1180): undefined reference to `pthread_join'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::(anonymous namespace)::create_current_thread_tls_key()':
(.text+0x2b): undefined reference to `pthread_key_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::get_current_thread_data()':
(.text+0x1b6): undefined reference to `pthread_getspecific'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::set_current_thread_data(boost::detail::thread_data_base*)':
(.text+0x1f6): undefined reference to `pthread_setspecific'
CMakeFiles/gw_miner.dir/bitcoin.cpp.o: In function `boost::asio::detail::posix_thread::~posix_thread()':
bitcoin.cpp:(.text._ZN5boost4asio6detail12posix_threadD2Ev[_ZN5boost4asio6detail12posix_threadD5Ev]+0x26): undefined reference to `pthread_detach'
CMakeFiles/gw_miner.dir/bitcoin.cpp.o: In function `boost::asio::detail::posix_thread::join()':
bitcoin.cpp:(.text._ZN5boost4asio6detail12posix_thread4joinEv[_ZN5boost4asio6detail12posix_thread4joinEv]+0x2b): undefined reference to `pthread_join'
CMakeFiles/gw_miner.dir/bitcoin.cpp.o: In function `boost::asio::detail::posix_thread::start_thread(boost::asio::detail::posix_thread::func_base*)':
bitcoin.cpp:(.text._ZN5boost4asio6detail12posix_thread12start_threadEPNS2_9func_baseE[_ZN5boost4asio6detail12posix_thread12start_threadEPNS2_9func_baseE]+0x29): undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
make[2]: *** [gw_miner] Error 1
make[1]: *** [CMakeFiles/gw_miner.dir/all] Error 2
make: *** [all] Error 2

12
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 13, 2013, 04:01:50 pm »

Any word on ypool's performance on a 3.4 Ghz i7  iMac?  I am seeing 100 HPM.

I get about 50-60 on a quad core i5.  On a 16 thread computer it only works fully if I run it four times, and they vary between 35 and 70 each.

13
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 13, 2013, 03:43:06 am »
haven't gotten a payout in a while, what is the min payout here again?

I believe it's manual payouts right now, and byte is sleeping.

14
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 13, 2013, 12:28:56 am »

15
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 13, 2013, 12:09:23 am »
Hey everyone... I am going to get some sleep.  If there is any problem with the pool PM user Stan or Lighthouse and they will be able to reach me.

What's the current payout system?  Is it once every 6 hours or something?

Pages: [1] 2 3 4