Pages:
Author

Topic: [ANN] ORCACOIN Helping Ocean Conservation - Coin Now IN ITS SECOND YEAR! - page 7. (Read 48838 times)

member
Activity: 83
Merit: 10
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=
 rpcpassword=
  #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
sr. member
Activity: 434
Merit: 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=
 rpcpassword=
  #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
member
Activity: 83
Merit: 10
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=
 rpcpassword=
  #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. 
sr. member
Activity: 434
Merit: 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=
 rpcpassword=
  #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

 
newbie
Activity: 1
Merit: 0
Are there any mining pool yet? Else I suppose I will try solo mining
member
Activity: 83
Merit: 10
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=
 rpcpassword=
  #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
member
Activity: 83
Merit: 10
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.
sr. member
Activity: 308
Merit: 250
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.
member
Activity: 83
Merit: 10
Hugh demand - please create some pools.  We will post them here and on the website.

newbie
Activity: 1
Merit: 0
good one..i will sup this one
legendary
Activity: 1232
Merit: 1002
WTS 100 Orca for BTC or LTC

contact me

I offer you 100 PENG and an extra of 100KARM!
Just because I'm good!
sq
sr. member
Activity: 294
Merit: 250
member
Activity: 83
Merit: 10
PLEASE CREATE NEW POOLS - HIGH DEMAND IS KNOCKING OUT OUR POOLS

member
Activity: 83
Merit: 10
OCEAN CONSERVATION FUND -  NOW HAS

      500,000 ORCACOINS!!!!
member
Activity: 70
Merit: 10
member
Activity: 83
Merit: 10
Dev contact exhangers please

We are in discussion with exchanges now.
sr. member
Activity: 490
Merit: 250
Dev contact exhangers please
full member
Activity: 144
Merit: 100
sr. member
Activity: 490
Merit: 250
WTS 100 Orca for BTC or LTC

contact me
member
Activity: 66
Merit: 10
lolwut 32k block mined already Cheesy
Pages:
Jump to: