 Show Posts
|
|
Pages: « 1 2 [3] 4 5 »
|
Just dropping by to let you guys know that its official: https://twitter.com/LazyCoinsYou're one of the first coins we have accepted at our exchange to be traded at launch, which will probably be the biggest launch for any altcoins exchange yet. Since our announcement 7 days ago we have already nearly reached 1000 followers and 20 altcoins aceepted. We are working hard to launch beta soon. So for ETA and updates please follow us https://twitter.com/LazyCoins. Retweet and show your support! ORCA will be paired with ltc, btc and doge  Fantastic news. Thank you for choosing to list Orcacoin. |
|
|
|
Your wallet is in sync (Please see my post). You should have received our email to you letting you know that we have credited your wallet with all the coins you mined in our pool. If you open your wallet it will show your balance. Please PM us if you cannot see your coins. We hope you will continue to support our coin. how can i know if i found bloick in solo mining? [/quote] I have sent you a PM detailing the coins we have sent to your wallet and how you can find them. When you are solo-mining, the blocks that you find should automatically be credited to your wallet. If your wallet is not crediting you with any blocks, please PM us with details of the mining software you are using. We can then give you additional help. |
|
|
|
|
Please do not worry about the message you are getting on your wallet at the moment. The wallet is in sync with the network as the wallets are all showing the same block number.
The wallet is fully functional and will show all the coins that you currently have.
The wallet message "out of sync" is there because, the network hashrate is very variable at the moment. This is to be expected so soon after launch. The wallet is taking time to calculate the expected number of blocks. It does not affect the wallet in anyway. Once more wallets and nodes come online this message will disappear.
|
|
|
|
|
Please support this coin. Share our passion for the world's oceans and help to conserve them for future generations. If enough people care this coin can make a difference.
|
|
|
|
|
Congratulation on the new exchange.
Please add ORCAcoin to your exchange. It's only two days old - but growing fast.
|
|
|
|
|
Please post the names of the Exchanges you want to list ORCAcoin.
|
|
|
|
no sync for me
When more nodes come online the wallet sync will improve, |
|
|
|
Hi Guys, Just wanted to drop by and let you guys know that we are considering adding Orcacoin to our exchange to be traded at launch, which will probably be the biggest launch for any altcoin exchange yet. Follow us on twitter @lazycoins and vote.https://bitcointalk.org/index.php?topic=471779.0Please click link to register your vote to add ORCAs Thank you |
|
|
|
|
It would be great to see OCRAcoin on your exchange.
Thanks
Orca Team
|
|
|
|
Hi Guys, Just wanted to drop by and let you guys know that we are considering adding Orcacoin to our exchange to be traded at launch, which will probably be the biggest launch for any altcoin exchange yet. Follow us on twitter @lazycoins and vote.https://bitcointalk.org/index.php?topic=471779.0Great news. We look forward to your launch. Thank you for supporting ORCAcoin. |
|
|
|
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.
I can't even see if I got paid considering the wallet is stuck at the last block. Wallet should update automatically now that new pools and nodes are being added. Please email your wallet address to: admin@orcacoin.info with the details of the email address you used to register at orcacoinpool. We will investigate and make sure you have your coins (and a bonus for the inconvenience). The orca team |
|
|
|
For me the wallet doesn't sync completely. Stops at the last block or sth.
Help?
The wallet is syncing slowly because we need more nodes on the network. We have added two nodes and hope that more will be added. |
|
|
|
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?
Unfortunately, we could not answer all queries during the launch. As we stated, we were launching a charity coin we were unprepared for the huge response. Thousands of wallets were being downloaded at the same time and the pool was overwhelmed. All miners have had their coins credited. ORCAcoin was developed to help Ocean Conservation Organisations. This is a long-term project. The pre-mine established the Fund and will allow for support and promotion of the coin. All donations to the charities will be logged on the website. This coin is now in the community - it will succeed if it is supported. We need more pools and more nodes to be added. Please continue to mine and trade this coin. |
|
|
|
|
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.
|
|
|
|
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 |
|
|
|
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. |
|
|
|
|
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
|
|
|
|
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. |
|
|
|
|
Hugh demand - please create some pools. We will post them here and on the website.
|
|
|
|
|
PLEASE CREATE NEW POOLS - HIGH DEMAND IS KNOCKING OUT OUR POOLS
|
|
|
|
|
