|
dbkeys
|
 |
May 31, 2018, 04:57:41 PM |
|
When will you rename the coin on poloniex ?
Bitmark will still be called "Bitmark", but we are changing the ticker symbol to MARKS (from the old BTM). Cryptopia.co.nz already has us actively trading and listed as MARKS. Poloniex has been advised that we wish to use the MARKS ticker symbol and they will be changing from BTM to MARKS, but they replied that the change is not trivial and may take a while. Fortunately, at Poloniex there is no confusion as there is no other coin there which uses BTM. Poloniex is always under maintenance (it will have worked 1 week in the last 12 months). It is very strange that CRYPTOPIA has VERY lower exchange rates than Poloniex, the current value of BITMARK is not truthful. In the real life is said to be an insider trading, in cryptocurrencies there are no laws or rules and this currency is proof of this. If I understand correctly, Poloniex has said that as soon as the new fork code is ready they will re-enable deposits and withdrawals. Once this happens, I imagine that the price will harmonize between the various exchanges; if not, that would present excellent arbitrage opportunities. |
DNS Seeder / Node Trackers |
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
dbkeys
|
|
June 06, 2018, 08:49:30 PM
Last edit: June 12, 2018, 11:40:29 AM by dbkeys |
|
Bitmark v0.9.7.0 is now available. Wallets Release Candidate 1 (RC1) wallets for Windows are available and soon to follow for MacOS & leading Linux versions. Fork is Active ! Please upgrade your nodes / wallets to v0.9.7 as soon as possible. Fork Activation will occur when 75 out of the last 100 blocks signal support Support is signaled with v4 blocks, used by Bitmark v0.9.7 New Features: 1) Difficulty Adujstment: custom DGWv3Mining Difficulty will be regulated by a custom Dark Gravity Wave v3, aided by a hashrate Surge Protector and Resurrector functions. The Surge Protector comes into play if there is a string of 9 blocks in-a-row by the same algorithm. The Resurrector activates whenever an algorith has not contributed blocks for over 160 minutes, something that is extremely unlikely to happen if the difficulty is well matched to hashrate. 2) Multiple Proof-of-Work Algorithms: 8 mPoWAdditional proof-of-work algorithms will be able to contribute blocks to the Bitmark blockchain. The complete list of algorithms is (SCrypt, SHA256d, Yescrypt, Argon2d, X17, Lyra2REv2, Equihash and Cryptonight). This means that miners will be able to mine Bitmark not only with Scrypt but with these additonal algos too, several of which are ASIC-resistant, thus democratizing the mininig and putting an end to the selfish-mining situations we have faced in the past. 3) Coin Emission Modulation: CEM v0.1Bitmark v0.9.7.0 also introduces Coin Emission Modulation, (CEM v0.1) which modulates up to 1/2 the mining subsidy (block reward) by reducing that half proportionately by the ratio of current hashrate to peak hashrate ( as experienced within the last year). The rationale behind this is to reduce coin emission when demand is relatively low (as sensed by reduced hashrate) and only emit the epoch's full reward when hashrate is at its peak. Regardless of hashrate, 50% of the epoch's full block subsidy (1/2 of 15 MARKS or 7.5 MARKS currently) is always given, to reward loyal miners supporting the Bitmark blockchain through low and high demand periods. |
DNS Seeder / Node Trackers |
|
|
|
Namduc
|
|
June 07, 2018, 05:32:50 AM |
|
Hi dbkeys!
When is the v0.9.7 version for Windows released?
|
|
|
|
|
|
dbkeys
|
|
June 07, 2018, 02:02:08 PM
Last edit: June 12, 2018, 11:44:01 AM by dbkeys |
|
|
DNS Seeder / Node Trackers |
|
|
|
Namduc
|
|
June 07, 2018, 02:33:59 PM |
|
It seems my wallet has a problem "out of sync" 7 day (s) behind. 
|
|
|
|
|
|
dbkeys
|
|
June 07, 2018, 03:51:39 PM |
|
It seems my wallet has a problem "out of sync" 7 day (s) behind. It might be necessary to open the wallet with more rights. Have this report from Candy Erdmann on Slack: " I have opened the program with full access rights and now its synchronizes" Also, make sure to connect to v0.9.7 nodes. Here is a list for your bitmark.conf file: addnode=108.170.1.134
addnode=139.162.122.138
addnode=139.162.128.92
addnode=139.162.232.242
addnode=169.0.84.73
addnode=172.104.157.27
addnode=173.255.252.140
addnode=204.68.122.12
addnode=204.68.122.40
addnode=216.240.168.226
addnode=216.240.168.227
addnode=216.240.168.228
addnode=42.118.134.98
addnode=79.143.180.57
addnode=85.10.51.66
addnode=94.189.240.43
addnode=94.23.33.83
addnode=95.90.243.191
|
DNS Seeder / Node Trackers |
|
|
|
bitChipper
|
|
June 07, 2018, 04:47:22 PM |
|
Good to see this project is still alive and rolling, holding a market on polo will be crucial...too bad they disabled the chatbox though. To me that was one of the best ways for bitmark to be seen and utilized.
You guys know if they will ever bring it back?
|
|
|
|
|
|
dbkeys
|
|
June 07, 2018, 05:02:30 PM |
|
Good to see this project is still alive and rolling, holding a market on polo will be crucial...too bad they disabled the chatbox though. To me that was one of the best ways for bitmark to be seen and utilized.
You guys know if they will ever bring it back?
Good question. It was definitely a very attractive part of the Polo experience. |
DNS Seeder / Node Trackers |
|
|
psycodad
Legendary
 Offline
Activity: 1605
Merit: 1568
精神分析的爸
|
|
June 07, 2018, 05:15:26 PM |
|
I am unable to compile the source under any Debian amd64 version (tried 8 and 9). On Debian 9 it seems impossible due to too new openssl version with errors like: ...
bignum.h: In function 'bool operator>(const CBigNum&, const CBigNum&)':
bignum.h:594:83: error: cannot convert 'const CBigNum*' to 'const BIGNUM* {aka const bignum_st*}' for argument ' ' to 'int BN_cmp(const BIGNUM*, const BIGNUM*)'
inline bool operator>(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) > 0); }
...
On Debian 8 I can overcome some c11 related errors with: ./autogen.sh && ./configure --with-incompatible-bdb --without-miniupnpc && CXXFLAGS="-std=c++11" make
But then I am stuck with the following compile errors: In file included from cryptonight/crypto/hash.c:35:0:
cryptonight/crypto/hash-ops.h:65:15: error: expected declaration specifiers or '...' before 'sizeof'
static_assert(sizeof(union hash_state) == 200, "Invalid structure size");
^
cryptonight/crypto/hash-ops.h:65:48: error: expected declaration specifiers or '...' before string constant
static_assert(sizeof(union hash_state) == 200, "Invalid structure size");
^
Makefile:1047: recipe for target 'cryptonight/crypto/hash.o' failed
make[3]: *** [cryptonight/crypto/hash.o] Error 1
Any pointers and hints would be much appreciated. TIA. |
|
|
|
kendie
Newbie
Offline
Activity: 13
Merit: 0
|
|
June 07, 2018, 06:08:56 PM |
|
Hi dbkeys!
When is the v0.9.7 version for Windows released?
Windows Wallets:Win64: https[Suspicious link removed] CheckSums (shasum -a 256)49a10a1240f2953a5519c83f944a0169a07986314e97e2e4e151ff607ae19ea3 bitmark-0.9.5-win32-rc1.setup.exe 76c0abb680ab867d6253c284cfcb0618d9c4e1e0039dd70da859d51006f137c7 bitmark-0.9.5-win64-rc1.setup. -- Wallets for MacOS and binaries for Raspberry Pi are next.It seems my wallet has a problem "out of sync" 7 day (s) behind. It might be necessary to open the wallet with more rights. Have this report from Candy Erdmann on Slack: " I have opened the program with full access rights and now its synchronizes" Also, make sure to connect to v0.9.7 nodes. Here is a list for your bitmark.conf file: addnode=108.170.1.134
addnode=139.162.122.138
addnode=139.162.128.92
addnode=139.162.232.242
addnode=169.0.84.73
addnode=172.104.157.27
addnode=173.255.252.140
addnode=204.68.122.12
addnode=204.68.122.40
addnode=216.240.168.226
addnode=216.240.168.227
addnode=216.240.168.228
addnode=42.118.134.98
addnode=79.143.180.57
addnode=85.10.51.66
addnode=94.189.240.43
addnode=94.23.33.83
addnode=95.90.243.191
not work. |
|
|
|
|
iso2000
Newbie
Offline
Activity: 107
Merit: 0
|
|
June 07, 2018, 06:20:57 PM |
|
Get some actual working nodes from the pool. Click on connections count. |
|
|
|
|
kendie
Newbie
Offline
Activity: 13
Merit: 0
|
|
June 07, 2018, 06:28:00 PM |
|
Get some actual working nodes from the pool. Click on connections count. THX,is working  |
|
|
|
|
kendie
Newbie
Offline
Activity: 13
Merit: 0
|
|
June 07, 2018, 06:35:49 PM |
|
Get some actual working nodes from the pool. Click on connections count. but now 7 day ago~and stop syn |
|
|
|
|
pedrocoin
Newbie
Offline
Activity: 15
Merit: 0
|
|
June 07, 2018, 08:06:46 PM
Last edit: June 07, 2018, 08:17:08 PM by pedrocoin |
|
if i update my windows wallet from 95 to 97 will i automaticly keep the coins i had?
still no deposit on poloniex and the fork seem to be done...
|
|
|
|
|
Matiel
Newbie
Offline
Activity: 34
Merit: 0
|
|
June 07, 2018, 08:36:39 PM |
|
some forecast to release the wallet at the Polo
|
|
|
|
|
|
dbkeys
|
|
June 07, 2018, 09:04:34 PM |
|
if i update my windows wallet from 95 to 97 will i automaticly keep the coins i had?
still no deposit on poloniex and the fork seem to be done...
It's always a good idea to make a backup of your wallet.dat file. I would make backups regularly. But to answer your question, the upgrade from v0.9.5 to v0.9.7 will keep the coins you have. It should not affect your wallet.dat file. |
DNS Seeder / Node Trackers |
|
|
pedrocoin
Newbie
Offline
Activity: 15
Merit: 0
|
|
June 07, 2018, 09:15:05 PM
Last edit: June 07, 2018, 09:51:27 PM by pedrocoin |
|
Yeah i regularly backups my wallets...
|
|
|
|
|
pedrocoin
Newbie
Offline
Activity: 15
Merit: 0
|
|
June 07, 2018, 09:48:18 PM |
|
I've installed it but it stop working and close by itself every few minutes... windows 64 bit version.. The last version was fine
|
|
|
|
|
HeldExpert
Copper Member
Newbie
Offline
Activity: 98
Merit: 0
|
|
June 07, 2018, 10:31:28 PM |
|
I've installed it but it stop working and close by itself every few minutes... windows 64 bit version.. The last version was fine
also does not work |
|
|
|
|
|
Namduc
|
|
June 08, 2018, 10:06:30 AM |
|
It seems my wallet has a problem "out of sync" 7 day (s) behind. It might be necessary to open the wallet with more rights. Have this report from Candy Erdmann on Slack: " I have opened the program with full access rights and now its synchronizes" Also, make sure to connect to v0.9.7 nodes. Here is a list for your bitmark.conf file: addnode=108.170.1.134
addnode=139.162.122.138
addnode=139.162.128.92
addnode=139.162.232.242
addnode=169.0.84.73
addnode=172.104.157.27
addnode=173.255.252.140
addnode=204.68.122.12
addnode=204.68.122.40
addnode=216.240.168.226
addnode=216.240.168.227
addnode=216.240.168.228
addnode=42.118.134.98
addnode=79.143.180.57
addnode=85.10.51.66
addnode=94.189.240.43
addnode=94.23.33.83
addnode=95.90.243.191
The wallet of t still can not be synchronized. It runs for a while, then automatically exits on my Window computer(Window 64 bit). |
|
|
|
|
|
