Bitcoin Forum
February 02, 2023, 12:42:27 PM *
News: Latest Bitcoin Core release: 24.0.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Economy / Scam Accusations / VirtualCoin possible scam on: February 02, 2017, 06:12:11 PM
This ANN: https://bitcointalk.org/index.php?topic=1756007.0

Reasons: not working source code. Wallet can not be compiled. OP owner deleting posts instead of answering questions surrounding this.

And proof below, my posts that were deleted.

Quote from: Bitcoin Forum
A reply of yours, quoted below, was deleted by the starter of a self-moderated topic. There are no rules of self-moderation, so this deletion cannot be appealed. Do not continue posting in this topic if the topic-starter has requested that you leave.

You can create a new topic if you are unsatisfied with this one. If the topic-starter is scamming, post about it in Scam Accusations.

Quote
Since the other topic is locked for some reason: https://bitcointalk.org/index.php?topic=1756007.0

...i am posting here.

Just a warning to everyone.

The source code of this coin is a mess, it can not be compiled normally: https://github.com/vcoin-z/virtualcoin/

The whole thing smells fishy... proceed with caution.


what do you mean he wants to try to fool or just a problematic source code only.

First of all it is strange that the main ANN topic is locked.

Second of all, the source is just wierd. It has an old genesis block and there are thousands of errors at compilation.

Third thing that is strange is that the github link was really hard to find... It was not posted in the ann, it was only posted in the tweet. And this source is old. Its like he or she posted it just to make it look good, thinking nobody would actually go test it and just use the compiled windows wallet on megaupload.

So yeah, I think its a scam of some sort. There might be malicious code in the windows wallet...honestly I don't know and I don't care that much.

Just wanted to give out a warning, that this is a strange launch of a coin and people should be careful.

Edit: I mean, the coin is launched and the OP says source and wallets coming soon. Who does that really? Smiley
2  Bitcoin / Bitcoin Technical Support / Bitcoin Core 12.1 Solo Mining Problem on: May 10, 2016, 07:43:59 PM
Since the update to 12.1 I can not solo mine anymore.

I am solo mining (as a joke of course) with one usb antminer u1 on the same machine that is running the node, it worked so far but with the new version I am getting this in bfgminer:

Code:

 [2016-05-10 21:33:30] No servers were found that could be used to get work from

 [2016-05-10 21:33:30] Please check the details from the list below of the servers you have input

 [2016-05-10 21:33:30] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers

Funny thing is, the bitcoind log reports a "create new block" message when I start the miner, not an "unauthorized rpc user/password error":

Code:
2016-05-10 19:32:41 CreateNewBlock(): total size 172240 txs: 323 fees: 5817514 sigops 960

But thats it, that is the one and only message I get regarding mining.

I know about this:

Code:
2016-05-10 19:29:21 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.

But it says soon, so not yet right?

Why is bitcoind not accepting a valid rpcuser and pasword that is in the bitcoin.conf file?

3  Alternate cryptocurrencies / Announcements (Altcoins) / [ANN][NEVA] NevaCoin | PoS | Blake2s | NO Premine | on: March 05, 2016, 01:47:06 PM
Nevacoin

The first decentralized cryptocurrency ever to be created as a gift for someone's birthday. At 1457344680 unix time is my girlfriend's 25th birthday (her name is Neva if that isn't obvious) and since she is abroad at the moment I figured this is the best gift I can give her remotely. Who wouldn't want a global decentralized peer to peer network cryptocurrency platform named after them as a birthday gift, right? Don't worry, I will also give her a less geeky gift when she comes back Smiley

Genesis block:

Code:
const char* pszTimestamp = "Happy 25th birthday Neva!!!";

        genesis.nTime    = 1457344680;
      

The coin was successfully launched on March 7th, 9:58AM (GMT) and is available for mining (for the next 14years) and staking since day one.

Name meaning:

Gender: F  Meaning of Neva: "white snow" Origin of Neva: Spanish


What is the purpose of this coin?

- 0% PoS, fixed block rewards ensure predictable supply increase.

- Unlike most of PoW/PoS Hybrids, this one will have a very long PoW phase. The network will stop accepting PoW blocks in approximately 14 years. The goal is to gain a mining chance, even to people that stumble upon it years later in the future.

- Gain some interest from the female half of the population (starting with Neva). Lets be honest the cryptocurrency community is still a sausage fest Smiley

- Blake2s mining algorithm.

- Blake2s PoS block hashing - friendly to low end hardware. Raspberry-Pi nodes...etc.

- Slow emmision. The PoW and PoS reward is 5 NEVAs. The reward will halve for both at block height 2628000. That is approximately 7 years until the first halving. After the second halving at block height 5256000 the PoW phase will be over, continued only by PoS with 1.25 NEVA reward, which will halve again in 2628000 blocks...etc.

- The low reward and long PoW phase is meant to avoid the insta-mine by handful of people.

Coin specifications:

Ticker:                       NEVA
Type:                         PoW/Pos2.0 hybrid
PoW algorithm:           Blake2s  (read more)
Difficulty retarget:       Every block
Block target:               91 seconds
Block reward:              5 NEVA  (both PoW and PoS have static rewards)
Max block size:            4MB
Coinbase maturity:      25 blocks
Block reward halving:   every 2628000 blocks (approx 7 years, probably less)
Last PoW block:           5256000 (in approx 14 years)
PoS start:                    from the first block
Minimum PoS age:        4 hours
Maximum PoS age:       no max (PoS 2.0)
Max coins:                   26 280 000 NEVAs (this amount will be reached at block 131400000, or in roughly 350 years)

Sum of the mining/staking schedule:

Halvig phase      Block Reward        New coins created    Total coins created     Approx Time (years)
0                       5                         13140000               13140000                  7
1                       2.5                      6570000                 19710000                  14
2                       1.25                    3285000                  22995000                  21
3                       0.625                  1642500                  24637500                  28
4                       0.3125                 821250                   25458750                  35
5                       0.15625               410625                   25869375                  42
6                       0.078125             205312.5                 26074687.5               49
7                       0.0390625            102656.25              26177343.75              56
8                       0.01953125          51328.125              26228671.88              63
9                       0.009765625        25664.0625            26254335.94              70
10                     0.0048828125      12832.03125           26267167.97              77
                 .                    .                      .
                 .                    .                      .
                 .                    .                      .


Network info:

P2P port: 7391
RPC port: 3791

Testnet P2P port: 17391
Testnet RPC port: 13791

Seed nodes are hard coded.

QT GUI Wallet Features:
-Integrated block explorer
-Two themes, default light theme and an optional funky dark theme

Daemon features:
-coockie authentication
   - You do not need the rpcuser/password parameters in the nevacoin.conf to run the daemon. You can still use them if you want, but if they are not provided an authentication cookie file will be generated in the .nevacoin directory and also deleted on shutdown. So one less thing you have to do if you want to run a headles node for staking.

Basic setup for daemon in nevacoin.conf file is:
Code:
daemon=1



Website




Exchanges

Freiexchange

Unnamed Exchange

Yobit



Block explorer

CryptoID



Social

Twitter

Facebook

 QQ group ID: 218602035   - Chinese IM platform QQ: http://im.qq.com/




Source


GitHub Source



Wallet download

Windows Executable


Donation address for further developement: NQDJrKGP3TNhKhKzaHMdg1Wk9FWCT4Nx3q


4  Bitcoin / Bitcoin Technical Support / bitcoind recieve version message from 127.0.0.1:8333 every two seconds on: May 05, 2015, 09:29:41 PM
Hello,

any idea what is causing this? It just goes on forever, every two seconds. I noticed today that bitcoind crashed, upon restarting it again I followed the log for a while and saw this. 

Code:
2015-05-05 21:19:59 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=516
2015-05-05 21:20:01 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=517
2015-05-05 21:20:02 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=518
2015-05-05 21:20:04 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=519
2015-05-05 21:20:06 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=520
2015-05-05 21:20:08 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=521
2015-05-05 21:20:09 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=522
2015-05-05 21:20:11 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=523
2015-05-05 21:20:13 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=524
2015-05-05 21:20:14 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=525
2015-05-05 21:20:16 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=526
2015-05-05 21:20:18 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=527
2015-05-05 21:20:20 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=528
2015-05-05 21:20:23 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=529
2015-05-05 21:20:25 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=530
2015-05-05 21:20:26 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=531
2015-05-05 21:20:29 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=532
2015-05-05 21:20:30 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=533
2015-05-05 21:20:32 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=534
2015-05-05 21:20:34 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=535
2015-05-05 21:20:37 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=536
2015-05-05 21:20:40 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=537
2015-05-05 21:20:42 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=538
2015-05-05 21:20:45 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=539
2015-05-05 21:20:46 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=540
2015-05-05 21:20:49 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=541
2015-05-05 21:20:51 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=542
2015-05-05 21:20:53 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=543
2015-05-05 21:20:54 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=544
2015-05-05 21:20:56 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=545
2015-05-05 21:20:57 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=546
2015-05-05 21:20:59 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=547
2015-05-05 21:21:01 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=548
2015-05-05 21:21:02 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=549
2015-05-05 21:21:04 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=550
2015-05-05 21:21:06 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=551
2015-05-05 21:21:08 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=552
2015-05-05 21:21:09 receive version message: /breadwallet:1.8/: version 70002, blocks=0, us=86.61.18.19:8333, peer=553
2015-05-05 21:21:09 Added time data, samples 34, offset -8 (+0 minutes)
2015-05-05 21:21:09 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=554
2015-05-05 21:21:12 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=555
2015-05-05 21:21:14 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=556
2015-05-05 21:21:16 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=557
2015-05-05 21:21:17 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=558
2015-05-05 21:21:21 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=559
2015-05-05 21:21:22 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=560
2015-05-05 21:21:23 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=561
2015-05-05 21:21:25 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=562
2015-05-05 21:21:27 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=563
2015-05-05 21:21:28 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=564
2015-05-05 21:21:31 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=565
2015-05-05 21:21:34 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=566
2015-05-05 21:21:36 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=567
2015-05-05 21:21:37 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=568
2015-05-05 21:21:39 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=569
2015-05-05 21:21:41 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=570
5  Bitcoin / Bitcoin Technical Support / bitcoind not accepting connections on 8333 on: March 31, 2015, 09:41:13 PM
Hello all,

I decided to run a full node to help out the network. I have a fast fiber connection, so I guess it would make a good contribution.

Everything already worked, but then I had to restart my server after a few days and since then, bitcoind does not accept connections anymore - it is still connected to the network and is updating the new blocks as they come...

Here is some more info:

I am running version 0.10.0 compiled from source on ubuntu server 14.04, no GUI, so only CLI tips please.

bitcoin.conf
Code:
server=1
daemon=1
rpcuser=bitcoinrpc
rpcpassword=xxxxxxxxx
rpcport=8332

bitcoind debug.log

Code:
2015-03-31 20:48:05 Bound to [::]:8333
2015-03-31 20:48:05 Bound to 0.0.0.0:8333
2015-03-31 20:48:05 init message: Loading block index...

netstat --ip -lpa gives me:
Code:
tcp        0      0 localhost:8332          *:*                     LISTEN      1533/bitcoind  
tcp        0      0 *:8333                  *:*                     LISTEN      1533/bitcoind  

A port scanning website gives me this:
Code:
My IP x.x.x.x is responding on port 8333 ().

I use a direct PPPoE connection, no router in between. And from the info provided above, my IP is reachable on 8333.

However according to blockchain.info and also https://getaddr.bitnodes.io/ my node is not reachable.

I googled all the options, but mostly people have problems with routers and port forwarding etc. Here the port is reachable, so it has to stop somewhere in bitcoind. The bitcoin.conf file does not have any options to even try solving this...

And btw, its not a general issue on the server, I can connect via SSH (21) from the outside normally and also from other ports...

Any help would be appreciated.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!