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

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://bitcointalksearch.org/topic/ann-lazycoins-crypto-currency-exchange-beta-launched-21st-july-2014-471779

Wallet should update automatically now that new pools and nodes are being added.  Please email your wallet address to: [email protected] 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

I can't even see if I got paid considering the wallet is stuck at the last block. 

Mining pool has been set up.

http://85.25.209.87:7535

Use your ORCA address as username and any password will work.

Example config cgminer (GPU Mining)


Example config minerd (CPU Mining)


Pool donations: 4RccNbHNouiuCvebS4cC4cajnKnKtFaDpC

I believe noone.
Apart from believing almost every coin maker merely intends to make a quick buck here and most of them are dishonest assholes as well. I don't believe anyone when they are talking about making a coin for charity. It's just not true.
 I wish it were different because honestly it's really annoying. If I were able to change it by making an honest cryptocurrency with honest people I'd do it, albeit I lack what is necessary to make it. Apart from honesty - I got that.

...AND A BONUS!!!!

Wow my Orca has been credited from the crashed pool. I guess there is a first time for everthing.

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.

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.  

other nodes?

i'm stopped synching at 33450 block

Let me help you. Start using your brains and stop mining this piece of garbage! Or do you believe any stranger on the internet without a proper plan or proof about donations to sea charity?

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

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?

Post the communication with charity if you're honest

Too much lemmings. They even mine 10% premined coins. They mine coins without a future plan!

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=
 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

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.   

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

could you post the proof for charity funds?