Bitmark

[TwinWinNerD]

What is wrong with the network? Shouldn't there be one block every 2 minutes? Right now there is a block every hour at most and they are nearly empty....

[1714095180]

1714095180

[1714095180]

1714095180

[1714095180]

1714095180

[Este Nuno]

What is wrong with the network? Shouldn't there be one block every 2 minutes? Right now there is a block every hour at most and they are nearly empty....

High difficulty and low profitability, so very few miners. So production is slowed. It's not too much of an issue yet as we haven't rolled out any of our services yet so demand for Bitmark is low right now. And the benefit is that production of BTM is very low, which is helping to restrict supply.

[coinsolidation]

Bitmark 0.9.3 Released

This version of Bitmark Core aligns with Bitcoin 0.9.3, including post release updates.

It also includes Bitmark specific changes most notably the private key format has changed, a converter can be found at http://bitmark.co/brain to swap between old and new keys.

Existing wallets, and backups will continue to work as expected, only exported keys / cold storage keys need to be converted before importing them to v0.9.3.

Release and downloads for Windows, Linux, and Mac: https://github.com/project-bitmark/bitmark/releases/tag/v0.9.3

Changes:

• Private key version change to 213 to align with common third party tools.
• Seed Nodes and Checkpoints updated.
• Make -proxy set all network types, avoiding a connect leak.
• Refactor Alert to use static methods.
• Avoid a segfault on getblock if it can’t read a block from disk
• Add paranoid return value checks in base58
• Don’t poll showmyip.com, it doesn’t exist anymore
• Add a way to limit deserialized string lengths and use it
• Increase IsStandard() scriptSig length
• Avoid querying DNS seeds, if we have open connections
• Remove a useless millisleep in socket handler
• Stricter memory limits on CNode
• Better orphan transaction handling
• Add -maxorphantx= and -maxorphanblocks= options for control over the maximum orphan transactions and blocks
• Check redeemScript size does not exceed 520 byte limit
• Ignore (and warn about) too-long redeemScripts while loading wallet
• fix ‘opens in testnet mode when presented with a BIP-72 link with no fallback’
• AvailableCoins: acquire cs_main mutex
• Fix unicode character display on MacOSX
• key.cpp: fail with a friendlier message on missing ssl EC support
• Remove bignum dependency for scripts
• Upgrade OpenSSL to 1.0.1i (see https://www.openssl.org/news/secadv_20140806.txt - just to be sure, no critical issues for Bitmark Core)
• Upgrade miniupnpc to 1.9.20140701
• Fix boost detection in build system on some platforms

Pfennig 0.9.3

Pfennig has also been updated to align with both Bitcoin v0.9.3 and Bitmark v0.9.3.  Source can be found at https://github.com/project-bitmark/pfennig


More

Bitcore, Insight-api, and Insight have all been updated recently.
A pull request with BTM support has been submitted to brainwallet.org.
http://bitmark.co/brain/ has been updated to produce both v0.9.3 and previous version private keys.

[statdude]

Thanks Mark, great to see steps forward on the roadmap
https://bitmark.aha.io/published/4457ddb73f8f65e4b34ace9b319a4942?page=1

[coinsolidation]

Bitmark BTM now on https://brainwallet.github.io/

[Ryse]

A little late to the project myself I see..oh well, time for new beginnings!

[pabloangello]

A little late to the project myself I see..oh well, time for new beginnings!

What you mean you are late, late in what sense?

[coinsolidation]

A little late to the project myself I see..oh well, time for new beginnings!

Welcome Ryse, if you would like an invitation to slack, where the community is most active, please pm myself or estenuno.

[Ryse]

A little late to the project myself I see..oh well, time for new beginnings!

What you mean you are late, late in what sense?

Late as in I just recently discovered this amazing coin. This topic has been quite a read so far. One of the top altcoin developers hands down.

[82ndabnmedic]

A little late to the project myself I see..oh well, time for new beginnings!

What you mean you are late, late in what sense?

Late as in I just recently discovered this amazing coin. This topic has been quite a read so far. One of the top altcoin developers hands down.

Wholeheartedly agree with your assessment...Additionally, I firmly believe Mark is one of the Top Developers within all of Crypto.

Thank You for taking interest in our Project & Welcome to the Community.

[pabloangello]

A little late to the project myself I see..oh well, time for new beginnings!

What you mean you are late, late in what sense?

Late as in I just recently discovered this amazing coin. This topic has been quite a read so far. One of the top altcoin developers hands down.

Its not too late We are still before the adoption phase (but probably not so long before). I suggest you join our Slack group and there always will be someone to answer your questions. Or just watch for view days how our conversations look like.

[15266]

Hi fellas :-) got myself a syncing issue. Downloaded the last qt but it says no block source available?
I apologize if the explanation to the problem is already posted somewhere, not very good with wallets I'm afraid.

[coinsolidation]

Hi fellas :-) got myself a syncing issue. Downloaded the last qt but it says no block source available?
I apologize if the explanation to the problem is already posted somewhere, not very good with wallets I'm afraid.

Strange, please close and reopen once or twice, it should fix it automatically.

The problem is likely that one of the seed nodes has gone down.  The code picks one at random to try on the first time you ever connect, if you are unfortunate enough to get one which has went offline, then you get this issue.  Simply restarting should fix it.  In the meantime, thank you for making us aware, I'll check all the main seed nodes to ensure they're running.

[15266]

Hi fellas :-) got myself a syncing issue. Downloaded the last qt but it says no block source available?
I apologize if the explanation to the problem is already posted somewhere, not very good with wallets I'm afraid.

Strange, please close and reopen once or twice, it should fix it automatically.

The problem is likely that one of the seed nodes has gone down.  The code picks one at random to try on the first time you ever connect, if you are unfortunate enough to get one which has went offline, then you get this issue.  Simply restarting should fix it.  In the meantime, thank you for making us aware, I'll check all the main seed nodes to ensure they're running.

darn you're right, it fixed itself. Thanks!

[leathan]

Ill sell you my time for them ?

[btcney]

I can't get my Bitmark wallet to sync, it's stuck at 4 hours.

[Este Nuno]

I can't get my Bitmark wallet to sync, it's stuck at 4 hours.

It's probably synced but due to slow blocks the client shows that it's not synced.

[btcney]

I can't get my Bitmark wallet to sync, it's stuck at 4 hours.

It's probably synced but due to slow blocks the client shows that it's not synced.

So I just wait?

[Este Nuno]

I can't get my Bitmark wallet to sync, it's stuck at 4 hours.

It's probably synced but due to slow blocks the client shows that it's not synced.

So I just wait?

It should sync when the next block is found. It's not really out of sync now, it just shows that it is.

[coinsolidation]

It should sync when the next block is found. It's not really out of sync now, it just shows that it is.

As EsteNuno says, the client is synchronized, you can verify this by checking the time of the last block on the explorer and comparing to your last block received.