both are looking good to me, i keep small amounts on exchanges, most is in the wallet, gets a healthy breather every 3 weeks   

 no ico or premine but devs do get a hefty slice of the pie. dyor

The Hemp Coin  ...

 PoS is still broken after 2 years, bit she still trades on trex   

are you using the newest wallet? if you are, go back! i tried the newest one and at first it was fine, but after a few days about 1/2 my balance dissapeared. when i reverted to the old wallet, everything OK   

about a year ago PoW was paused for a month or so, PoS kept the chain moving just fine

  as starman said but not the oldest! send the youngest coin you have so you destroy only the least amount of coinage

 try sending a smaller amount
or, you can use coin control to see if you only have hundreds of small inputs to send. if that is the case you may need to use coin control consolidate into larger blocks

  i agree w/'nit and pokey, let's fine tune our aims, exactly, to develop a product that is truly  attractive to investors and n00bs, and stick with it.

 also, in regards to the new wallet, it is working much better, but i need to report that i just recently had some trouble, although i think the root of it is in the bitcoin core code but idk...
first let me say that where i mine from my desktop 24/7, it is a constant stress test on the whole system, i experience frequent resets, bluescreens, etc; also i run about a dozen PoS wallets at any given time.
 so, after a recent unexpected hard shutdown, the fly wallet would not start with any of the backup .dats i had, (well, i tried about 10 of many, including the one that had started the previous session) no go so ok import keys
  (again i don't think fly is unique with this problem, but does i think express the worst instance of it; for example after this event none of the other wallets i was running had any trouble starting back up)
 did that, (balance is correct) but the results bring me here to question. when you import a private key, shouldn't the new address(s) show up on the receive tab after a restart/rescan? for me this is not the case
 also when importing, i did (had to, i think) specify a label for each addy, but the specification did not survive. i'm using win 8.1

 receive tab (after import): new addy only
    

 coin control
  

 so can anyone land a hand here please?  i've only been mining a little while, so the problem isn't too big; only ~7-8k coin in the orig wallet,  hate loosing things tho

can i just manually import the wallet.json file and send them to myself?

[edit] i fixed it, found the ansa @ https://forum.sia.tech/topic/254/recover-account-with-seed/2

 i'm in the US, was off earlier, but it's back on for sure - maybe try a reboot or an alt ip

  it's working again

 

  use www.virustotal.com to scan small files (like wallets) it uses +/- 50 AV engines to scan, it's prolly faster than using your onboard AV

                            - BUT remember, serious hackers will have no problem hiding their payload

                                                                                      

 would be nice to see the site all fixed and paying properly    

 hi ppl i'm having a little problem that i need some help with

i have the sia wallet installed on my pc (win 8.1, plenty RAM, CPU & storage) it has stopped working, with the message 'siad has unexpectedly stopped'. after many restarts, it still won't start, so i sync'd a copy of a fresh wallet on my laptop (it's working fine) and i find i need help with the CLI to import the seed.

i've tried:
./siac wallet load seed [seed]

but that doesn't seem to do it; siad returns:
Usage:
  ./siac wallet load seed [flags]

Global Flags:
  -a, --addr string   which host/port to communicate with (i.e. the host/port siad is listening on) (default "localhost:9980")

not sure what it's asking for?

thanks

  sorry to have to inform you, staking has been broken for about 2 years. idk why no one's been able to fix it, but there it is.

 thanks 8-bit, i will try that, tho meanwhile i moved the wallet to my laptop and its staking again

Dear Reddheads,

Yesterday Reddcoin lead dev @gnasher announced the release of Reddcoin v2.0.

This release marks a major milestone in the history of Reddcoin, as the cryptocurrency shifts from being a Litecoin-derived project to following the Bitcoin codebase.

This move enables @gnasher and others working on the project to bring Bitcoin development to Reddcoin.

Reddcoin v2.0 includes important security upgrades and users are strongly recommend to upgrade now.

The accompanying notes released by @gnasher follow below. Go to the end of the notes for links directly to the binaries and source code on Github.

Kudos to John for bringing this major work to fruition; congratulations to the community for the brand new wallet!
 

Reddibrek

Chief Editor

Reddcoin Core 2.0.0 release notes

Version 2.0.0 is the official release version of Reddcoin Core. On top of the new features, this update contains very important security fixes and all users MUST upgrade to this version as soon as possible. Details on several vulnerabilities were made public by the Bitcoin team (Official Bitcoin warning) regarding the issues. It is particularly important that users who are staking do upgrade, as once BIP 66 is enforced, version 3 blocks will be rejected from the network entirely.

Reddcoin 2.0.0 is a complete rebuild based off Bitcoin 0.9. This means in terms of the code-base we introduced all the changes up to Bitcoin 0.9.5 into this version of Reddcoin Core.

We have also included a couple of features from the 0.10 build including a connected peers tab and bandwidth monitoring.

We therefore suggest to read the release notes of Bitcoin up to and including 0.9.

v2.0.0 is a recommended update for all users.
 

Notable changes
For further explanation of these, see the above mentioned Bitcoin release notes.

    Code-base switched to Bitcoin

In efforts to improve the fast adoption of upstream changes, Reddcoin was switched from using Litecoin to Bitcoin code base.

    New utility applications

Reddcoin-cli for RPC command line functionality. Moving to split the client and server components from reddcoind.

    Faster synchronization

Reddcoin Core 2.0.0 includes parallel block synchronization to greatly reduce the initial blockchain synchronization time.

    Strict signature encoding (BIP66)

This release activates BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (4). These rules will only activate once a certain number of blocks are mined with this new version. It will take effect after 85% of the network (6120/7200 blocks) are generating v4 blocks (7200 blocks is equivilant to 5 days worth of blocks).

NOTE: This is not a hard fork, as all existing wallets will accept version 4 blocks, although they'll fail to enforce the new requirements.

    Staking
Once the above rule is activated, the network will reject the creation of version (3) blocks (stakes on earlier clients e.g v1.4.1). Transactions using earlier clients will be accepted by the network.

    RPC access changes

RPC access now supports binary network addresses. This means that you can specify a single IP address, a CIDR network address or a netmask for accessing the RPC service. Please note, wildcard string matching no longer works and will display an error in the debug.log file when you attempt to use use a wildcard string in the rpcallowip= variable, either as a config setting or launch parameter.

Before
   

After

rpcallowip=10.0.0.1
   

rpcallowip=10.0.0.1

rpcallowip=10.0.0.*
   

rpcallowip=10.0.0.0/24

rpcallowip=10.0.*
   

rpcallowip=10.0.0.0/16

rpcallowip=*
   

rpcallowip=::/0

rpcallowip=192.168.1.*
   

rpcallowip=192.168.1.1/255.255.255.0

Note: IPv6 addresses can also be used.



Reddcoin Core 2.0.0 release notes

Version 2.0.0 is the official release version of Reddcoin Core. On top of the new features, this update contains very important security fixes and all users MUST upgrade to this version as soon as possible. Details on several vulnerabilities were made public by the Bitcoin team (Official Bitcoin warning) regarding the issues. It is particularly important that users who are staking do upgrade, as once BIP 66 is enforced, version 3 blocks will be rejected from the network entirely.

Reddcoin 2.0.0 is a complete rebuild based off Bitcoin 0.9. This means in terms of the code-base we introduced all the changes up to Bitcoin 0.9.5 into this version of Reddcoin Core.

We have also included a couple of features from the 0.10 build including a connected peers tab and bandwidth monitoring.

We therefore suggest to read the release notes of Bitcoin up to and including 0.9.

v2.0.0 is a recommended update for all users.
 

Notable changes

For further explanation of these, see the above mentioned Bitcoin release notes.

    Code-base switched to Bitcoin

In efforts to improve the fast adoption of upstream changes, Reddcoin was switched from using Litecoin to Bitcoin code base.

    New utility applications

Reddcoin-cli for RPC command line functionality. Moving to split the client and server components from reddcoind.

    Faster synchronization

Reddcoin Core 2.0.0 includes parallel block synchronization to greatly reduce the initial blockchain synchronization time.

    Strict signature encoding (BIP66)

This release activates BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (4). These rules will only activate once a certain number of blocks are mined with this new version. It will take effect after 85% of the network (6120/7200 blocks) are generating v4 blocks (7200 blocks is equivilant to 5 days worth of blocks).

NOTE: This is not a hard fork, as all existing wallets will accept version 4 blocks, although they'll fail to enforce the new requirements.

    Staking

Once the above rule is activated, the network will reject the creation of version (3) blocks (stakes on earlier clients e.g v1.4.1). Transactions using earlier clients will be accepted by the network.

    RPC access changes

RPC access now supports binary network addresses. This means that you can specify a single IP address, a CIDR network address or a netmask for accessing the RPC service. Please note, wildcard string matching no longer works and will display an error in the debug.log file when you attempt to use use a wildcard string in the rpcallowip= variable, either as a config setting or launch parameter.

Before
   

After

rpcallowip=10.0.0.1
   

rpcallowip=10.0.0.1

rpcallowip=10.0.0.*
   

rpcallowip=10.0.0.0/24

rpcallowip=10.0.*
   

rpcallowip=10.0.0.0/16

rpcallowip=*
   

rpcallowip=::/0

rpcallowip=192.168.1.*
   

rpcallowip=192.168.1.1/255.255.255.0

Note: IPv6 addresses can also be used.
 

    Stakeminer will wait for both the blockchain and network

This release will allow the staking of wallets that are not encrypted. Previously, if a wallet was not encrypted, the wallet would attempt to stake blocks as they were being downloaded. The wallet will now wait before staking is enabled.

It is however highly recommended to encrypt your wallet for your own peace of mind.

    QT Debug window includes network and peer details

An addition to the QT wallet is the network graph tab to visually monitor network usage and the peers details tab to display other attached nodes.

    DNS Seeds added

Additional dns seeds (dnsseed.redd.ink/testnet-dnsseed.redd.ink) for main and testnet to create some resilience for the network discovery.
 

General comments

Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Reddcoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Reddcoin Core completely before you make a copy of your wallet.dat.

 SHA256

c349881b9ea4496cac3f348647317d1b585306fbdfff57bb4fa2687cf0148bfb *reddcoin-2.0.0.0-linux.tar.gz
f34eb8f1929d0b10d400834cf89e2db417060e5e7437e20e3557fda685614f9c *reddcoin-2.0.0.0-osx-signed.dmg
547c647fc61772288f282dda021861dc11b902b780915f4cb7ccb4878f260808 *reddcoin-2.0.0.0-win.zip
e515ff56e675c3d60b4203feedb387a1a906a0171977ed25c5294cf4563f4a22 *reddcoin-2.0.0-win32-setup.exe
e2e15bc05d3460a6f1d1132db492540318dd343136ceb3e89986eae8edd1fa3c *reddcoin-2.0.0-win64-setup.exe
dfce44c9ae1d6a6cd3a7f1ac8f0730a427b7b2162f94f2bac177cb027c5628c8 *bootstrap.dat.xz

Downloads

    bootstrap.dat.xz (1020 MB)

    reddcoin-2.0.0-win32-setup.exe (11.3 MB)

   reddcoin-2.0.0-win64-setup.exe (12.1 MB)

    reddcoin-2.0.0.0-linux.tar.gz (36 MB)

    reddcoin-2.0.0.0-osx-signed.dmg (17.4 MB)

    reddcoin-2.0.0.0-win.zip (61.3 MB)

    SHA256SUMS.asc (576 Bytes)

    Source code (zip)

    Source code (tar.gz)

 imo j-c wants to market a finished product that may take the world's attention and focus it on a reasonable replacement for BTC

    sensible outlook in imo, why bring half-finished  half-started crap to market, just because everyone else in crypto (except one or two) is doing exactly that for a quick but short $buck$

  john has shit on my efforts too (worked hard to get vnl on accepted cryptopia) but i won't take that personally, he wants what will fit in with his outlook, and why not? it is his (and our, lol) baby

  interesting opinion, maybe fly&co can put some daytraders to work

  https://bitcointalk.org/index.php?topic=487814.msg15927621#msg15927621

here, i put mine up. it is clean
 mazacoin 0.9.0.1

idk if it's the latest; dL july 2015

https://mega.nz/#!Nt43SRTS!TxQoJh_XlWlaJGFBSEr4sh0moNdNZRDLqxJ3IxAygX4