Bitcoin Forum
December 12, 2017, 03:26:56 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 »  All
  Print  
Author Topic: [ANN] ORCACOIN Helping Ocean Conservation - Coin Now IN ITS SECOND YEAR!  (Read 48560 times)
sq
Sr. Member
****
Offline Offline

Activity: 294


View Profile WWW
February 21, 2014, 10:25:34 AM
 #241

hot hot coin  Shocked Shocked

1513049216
Hero Member
*
Offline Offline

Posts: 1513049216

View Profile Personal Message (Offline)

Ignore
1513049216
Reply with quote  #2

1513049216
Report to moderator
1513049216
Hero Member
*
Offline Offline

Posts: 1513049216

View Profile Personal Message (Offline)

Ignore
1513049216
Reply with quote  #2

1513049216
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
serje
Legendary
*
Offline Offline

Activity: 1106


Ibiza baby!


View Profile
February 21, 2014, 10:30:20 AM
 #242

WTS 100 Orca for BTC or LTC

contact me

I offer you 100 PENG and an extra of 100KARM!
Just because I'm good!

guodeng
Newbie
*
Offline Offline

Activity: 1


View Profile
February 21, 2014, 10:36:05 AM
 #243

good one..i will sup this one
orcacoin
Member
**
Offline Offline

Activity: 83


View Profile
February 21, 2014, 11:04:31 AM
 #244

Hugh demand - please create some pools.  We will post them here and on the website.

thisisnotmyltcusername
Sr. Member
****
Offline Offline

Activity: 252



View Profile
February 21, 2014, 11:40:46 AM
 #245

so huge you have to spam your own thread every 3 posts to tell us it's "huge" and beg for people to jump on board, the only huge thing here is your pile of premined scamcoins, no sane exchanger will ever accept such a grotesque scam, just die already.

orcacoin
Member
**
Offline Offline

Activity: 83


View Profile
February 21, 2014, 11:53:06 AM
 #246

so huge you have to spam your own thread every 3 posts to tell us it's "huge" and beg for people to jump on board, the only huge thing here is your pile of premined scamcoins, no sane exchanger will ever accept such a grotesque scam, just die already.

This coin is a charity coin with a pre-announced premine of 1% for the Charity Fund.  This is not a scam coin.  We need new pools as the current demand has knocked our pools out.  Please help.
orcacoin
Member
**
Offline Offline

Activity: 83


View Profile
February 21, 2014, 12:02:14 PM
 #247

Please make some pools - here is the conf file  -

Sample orcacoin.conf file
 
 # Network-related settings:
  # Run on the test network instead of the real bitcoin network.
  testnet=0
  # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
  ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 addnode=62.254.202.134
 addnode=62.254.202.137
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=62.254.202.137
  # Maximum number of inbound+outbound connections.
 #maxconnections=
  # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
  server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<your user name>
 rpcpassword=<your super secret password>
  #rpcuser=
 #rpcpassword=
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 #rpctimeout=30
  # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 # rpcallowip=62.254.202.*
  # Listen for RPC connections on this TCP port:
 #rpcport=7537
  # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 # rpcconnect=192.168.1.33
  # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 rpcssl=0
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 # Miscellaneous options
  # Set gen=1 to attempt to generate bitcoins
 gen=0
  # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
  # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 # User interface options
  # Start Bitcoin minimized
 #min=1
  # Minimize to the system tray
 #minimizetotray=1
lovetomine
Newbie
*
Offline Offline

Activity: 1


View Profile
February 21, 2014, 02:32:39 PM
 #248

Are there any mining pool yet? Else I suppose I will try solo mining
Mrjitter
Sr. Member
****
Offline Offline

Activity: 252



View Profile
February 21, 2014, 02:39:52 PM
 #249

Please make some pools - here is the conf file  -

Sample orcacoin.conf file
 
 # Network-related settings:
  # Run on the test network instead of the real bitcoin network.
  testnet=0
  # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
  ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 addnode=62.254.202.134
 addnode=62.254.202.137
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=62.254.202.137
  # Maximum number of inbound+outbound connections.
 #maxconnections=
  # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
  server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<your user name>
 rpcpassword=<your super secret password>
  #rpcuser=
 #rpcpassword=
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 #rpctimeout=30
  # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 # rpcallowip=62.254.202.*
  # Listen for RPC connections on this TCP port:
 #rpcport=7537
  # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 # rpcconnect=192.168.1.33
  # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 rpcssl=0
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 # Miscellaneous options
  # Set gen=1 to attempt to generate bitcoins
 gen=0
  # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
  # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 # User interface options
  # Start Bitcoin minimized
 #min=1
  # Minimize to the system tray
 #minimizetotray=1


we dont need more pools, we need good coins, not more SHITCOINS

 

orcacoin
Member
**
Offline Offline

Activity: 83


View Profile
February 21, 2014, 02:43:34 PM
 #250

Please make some pools - here is the conf file  -

Sample orcacoin.conf file
 
 # Network-related settings:
  # Run on the test network instead of the real bitcoin network.
  testnet=0
  # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
  ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 addnode=62.254.202.134
 addnode=62.254.202.137
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=62.254.202.137
  # Maximum number of inbound+outbound connections.
 #maxconnections=
  # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
  server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<your user name>
 rpcpassword=<your super secret password>
  #rpcuser=
 #rpcpassword=
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 #rpctimeout=30
  # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 # rpcallowip=62.254.202.*
  # Listen for RPC connections on this TCP port:
 #rpcport=7537
  # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 # rpcconnect=192.168.1.33
  # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 rpcssl=0
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 # Miscellaneous options
  # Set gen=1 to attempt to generate bitcoins
 gen=0
  # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
  # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 # User interface options
  # Start Bitcoin minimized
 #min=1
  # Minimize to the system tray
 #minimizetotray=1


we dont need more pools, we need good coins, not more SHITCOINS

 

We agree - thats why we developed ORCACOIN!!!  A Coin designed to give something back. 
Mrjitter
Sr. Member
****
Offline Offline

Activity: 252



View Profile
February 21, 2014, 02:59:16 PM
 #251

Please make some pools - here is the conf file  -

Sample orcacoin.conf file
 
 # Network-related settings:
  # Run on the test network instead of the real bitcoin network.
  testnet=0
  # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
  ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 addnode=62.254.202.134
 addnode=62.254.202.137
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=62.254.202.137
  # Maximum number of inbound+outbound connections.
 #maxconnections=
  # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
  server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<your user name>
 rpcpassword=<your super secret password>
  #rpcuser=
 #rpcpassword=
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 #rpctimeout=30
  # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 # rpcallowip=62.254.202.*
  # Listen for RPC connections on this TCP port:
 #rpcport=7537
  # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 # rpcconnect=192.168.1.33
  # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 rpcssl=0
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 # Miscellaneous options
  # Set gen=1 to attempt to generate bitcoins
 gen=0
  # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
  # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 # User interface options
  # Start Bitcoin minimized
 #min=1
  # Minimize to the system tray
 #minimizetotray=1


we dont need more pools, we need good coins, not more SHITCOINS

 

We agree - thats why we developed ORCACOIN!!!  A Coin designed to give something back. 

Then make your own pool, we have more coins to mine

orcacoin
Member
**
Offline Offline

Activity: 83


View Profile
February 21, 2014, 03:09:14 PM
 #252

Please make some pools - here is the conf file  -

Sample orcacoin.conf file
 
 # Network-related settings:
  # Run on the test network instead of the real bitcoin network.
  testnet=0
  # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
  ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 addnode=62.254.202.134
 addnode=62.254.202.137
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=62.254.202.137
  # Maximum number of inbound+outbound connections.
 #maxconnections=
  # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
  server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<your user name>
 rpcpassword=<your super secret password>
  #rpcuser=
 #rpcpassword=
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 #rpctimeout=30
  # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 # rpcallowip=62.254.202.*
  # Listen for RPC connections on this TCP port:
 #rpcport=7537
  # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 # rpcconnect=192.168.1.33
  # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 rpcssl=0
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 # Miscellaneous options
  # Set gen=1 to attempt to generate bitcoins
 gen=0
  # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
  # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 # User interface options
  # Start Bitcoin minimized
 #min=1
  # Minimize to the system tray
 #minimizetotray=1


we dont need more pools, we need good coins, not more SHITCOINS

 

We agree - thats why we developed ORCACOIN!!!  A Coin designed to give something back. 

Then make your own pool, we have more coins to mine

We did have a pool which crashed due to the number of people trying to mine it.  Before we restart our pool to want to ensure everybody who mined gets their coins.  In the meantime, we recommended hashfever and due to the demand, they also crashed.  That is why we are asking for more pools.

Enjoy your mining Mr Jitters
ciocgun
Sr. Member
****
Offline Offline

Activity: 476


View Profile WWW
February 21, 2014, 03:27:38 PM
 #253

could you post the proof for charity funds?
Mrjitter
Sr. Member
****
Offline Offline

Activity: 252



View Profile
February 21, 2014, 03:30:42 PM
 #254

Please make some pools - here is the conf file  -

Sample orcacoin.conf file
 
 # Network-related settings:
  # Run on the test network instead of the real bitcoin network.
  testnet=0
  # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
  ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 addnode=62.254.202.134
 addnode=62.254.202.137
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=62.254.202.137
  # Maximum number of inbound+outbound connections.
 #maxconnections=
  # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
  server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<your user name>
 rpcpassword=<your super secret password>
  #rpcuser=
 #rpcpassword=
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 #rpctimeout=30
  # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 # rpcallowip=62.254.202.*
  # Listen for RPC connections on this TCP port:
 #rpcport=7537
  # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 # rpcconnect=192.168.1.33
  # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 rpcssl=0
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 # Miscellaneous options
  # Set gen=1 to attempt to generate bitcoins
 gen=0
  # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
  # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 # User interface options
  # Start Bitcoin minimized
 #min=1
  # Minimize to the system tray
 #minimizetotray=1


we dont need more pools, we need good coins, not more SHITCOINS

 

We agree - thats why we developed ORCACOIN!!!  A Coin designed to give something back. 

Then make your own pool, we have more coins to mine

We did have a pool which crashed due to the number of people trying to mine it.  Before we restart our pool to want to ensure everybody who mined gets their coins.  In the meantime, we recommended hashfever and due to the demand, they also crashed.  That is why we are asking for more pools.

Enjoy your mining Mr Jitters

Your pool stole many coins for many users ..... that is not a crash that is SCAM


orcacoin
Member
**
Offline Offline

Activity: 83


View Profile
February 21, 2014, 03:39:43 PM
 #255

No - our pool did not steal any coins. 

The pool went down and caused a delay crediting all the coins mined to some of the accounts.  This is being done now.  Most of the miners have already received their coins. 

Why would we steal coins?  That does not help the charities we are trying to support.  We already have a large fund for the charities of over 500,000 coins.   
















minerator
Newbie
*
Offline Offline

Activity: 14


View Profile
February 21, 2014, 03:48:21 PM
 #256

Please make some pools - here is the conf file  -

Sample orcacoin.conf file
  
 # Network-related settings:
  # Run on the test network instead of the real bitcoin network.
  testnet=0
  # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
  ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 addnode=62.254.202.134
 addnode=62.254.202.137
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=62.254.202.137
  # Maximum number of inbound+outbound connections.
 #maxconnections=
  # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
  server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<your user name>
 rpcpassword=<your super secret password>
  #rpcuser=
 #rpcpassword=
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 #rpctimeout=30
  # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 # rpcallowip=62.254.202.*
  # Listen for RPC connections on this TCP port:
 #rpcport=7537
  # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 # rpcconnect=192.168.1.33
  # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 rpcssl=0
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 # Miscellaneous options
  # Set gen=1 to attempt to generate bitcoins
 gen=0
  # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
  # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 # User interface options
  # Start Bitcoin minimized
 #min=1
  # Minimize to the system tray
 #minimizetotray=1


we dont need more pools, we need good coins, not more SHITCOINS

 

We agree - thats why we developed ORCACOIN!!!  A Coin designed to give something back.  

Then make your own pool, we have more coins to mine

We did have a pool which crashed due to the number of people trying to mine it.  Before we restart our pool to want to ensure everybody who mined gets their coins.  In the meantime, we recommended hashfever and due to the demand, they also crashed.  That is why we are asking for more pools.

Enjoy your mining Mr Jitters
Quote from: Mrjitter on Today at 02:59:16 PM
Quote from: orcacoin on Today at 02:43:34 PM
Quote from: Mrjitter on Today at 02:39:52 PM
Quote from: orcacoin on Today at 12:02:14 PM
Please make some pools - here is the conf file  -

Sample orcacoin.conf file
 
 # Network-related settings:
  # Run on the test network instead of the real bitcoin network.
  testnet=0
  # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
  ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 addnode=62.254.202.134
 addnode=62.254.202.137
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=62.254.202.137
  # Maximum number of inbound+outbound connections.
 #maxconnections=
  # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
  # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
  server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<your user name>
 rpcpassword=<your super secret password>
  #rpcuser=
 #rpcpassword=
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 #rpctimeout=30
  # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 # rpcallowip=62.254.202.*
  # Listen for RPC connections on this TCP port:
 #rpcport=7537
  # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 # rpcconnect=192.168.1.33
  # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 rpcssl=0
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 # Miscellaneous options
  # Set gen=1 to attempt to generate bitcoins
 gen=0
  # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
  # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 # User interface options
  # Start Bitcoin minimized
 #min=1
  # Minimize to the system tray
 #minimizetotray=1
Bfljosh
Hero Member
*****
Offline Offline

Activity: 616


Skol!


View Profile
February 21, 2014, 03:59:46 PM
 #257

if you could remove your scamcoin at the same time to clean up the air , thanks in advance  Cheesy

timkin555 pushed to master at orcacoin 10 days ago
timkin555 created repository spicecoin  a month ago
timkin555 created repository noticoin  a month ago
timkin555 created repository meccacoin  a month ago
timkin555 created repository galacoin  a month ago
timkin555 created repository skicoin  a month ago
timkin555 created repository perkycoin  a month ago
timkin555 created repository godzillacoin  a month ago
timkin555 created repository nipcoin  a month ago
timkin555 created repository willycoin  a month ago
timkin555 created repository pussycoin  a month ago
timkin555 created repository beavercoin  a month ago
timkin555 created repository aacoin  a month ago
timkin555 created repository boatcoin  a month ago
timkin555 created repository lovecoin  a month ago
timkin555 created repository pinkcoin  a month ago
timkin555 created repository lynxcoin  a month ago
timkin555 created repository foxycoin  a month ago
timkin555 created repository truckercoin  a month ago
timkin555 created repository chevycoin  a month ago
timkin555 created repository truckcoin  a month ago

https://github.com/timkin555?tab=activity

good luck to all guys  Cheesy

LOL! I think ill skip this one.

+1



Sorry guys - we did not know the person who carried out the setup work had done this.  We will not work with them again.  We believe in our coin and dont want it lowered in this way.



could you keep your retard bullsh*t for your goldfish please ? only him could swallow that
btw google is fun :


Orcacoin Mining Pool I Statistics
62.254.202.134/php-mpos/.../index.php?...1‎

23 janv. 2014 -
1, aaran, 78,306
2, timkin444, 7,466
3, timkin111, 5,194
4, ichiko, 389
5, timkin555, 219



nice find !

if i could i would hold these pricks heads under water Smiley

there is a few crafty ways to track these pricks too i was emailed a creative way of doing it months back by a concerned user.

this scam shit has to stop !

enough already !

this forum should step up and start some new rules..

open your fucking eyes idiots

Too much lemmings. They even mine 10% premined coins. They mine coins without a future plan!
ciocgun
Sr. Member
****
Offline Offline

Activity: 476


View Profile WWW
February 21, 2014, 03:59:50 PM
 #258

No - our pool did not steal any coins.  

The pool went down and caused a delay crediting all the coins mined to some of the accounts.  This is being done now.  Most of the miners have already received their coins.  

Why would we steal coins?  That does not help the charities we are trying to support.  We already have a large fund for the charities of over 500,000 coins.  


Post the communication with charity if you're honest
Bfljosh
Hero Member
*****
Offline Offline

Activity: 616


Skol!


View Profile
February 21, 2014, 04:01:35 PM
 #259

So dev where is your donation plan? Where is the communication between Orcacoin and the sea charity organisations? To me it still looks like a cheap marketing trick to get goodwill. Pics or it didn't happen!

also: I've asked very legit questions yesterday, you did not answer one of them! Is this how a dev should communicate with his miners and investors?
wawaderwaran
Newbie
*
Offline Offline

Activity: 24


View Profile
February 21, 2014, 04:39:46 PM
 #260

For me the wallet doesn't sync completely. Stops at the last block or sth.
Help?

RIC RSxLPaQCBfEhtiPEWCB26iHNtR4tmf4Ed7
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!