gjhiggins



Offline



Activity: 1946

Merit: 1134









LegendaryActivity: 1946Merit: 1134 Re: [ANN][Datacoin - DTC]2017 New Clients, New Developers October 17, 2017, 05:02:56 PM #161 Quote from: AtomSea on October 14, 2017, 10:42:20 PM Am I seeing blocks that are substantially under 60 seconds here (contrary to what we advertise) ?



That perception is reinforced by what I'm seeing on the Datacoin ACME: http: //tessier.bel-epa.com:5059 (select Blocks->Browse the recent blockchain to see intervals for the last 100 blocks)



(Apologies for the unconscionable length of time it's taking me to get round to polishing up/finishing off the Datacoin ACME. Once again, I've taken on far too much and am having to plough through it.)



Cheers



Graham

That perception is reinforced by what I'm seeing on the Datacoin ACME:(select Blocks->Browse the recent blockchain to see intervals for the last 100 blocks)(Apologies for the unconscionable length of time it's taking me to get round to polishing up/finishing off the Datacoin ACME. Once again, I've taken ontoo much and am having to plough through it.)CheersGraham

Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee. ertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertised sites are not endorsed by the Bitcoin Forum. They maybe unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.

embii



Offline



Activity: 45

Merit: 3







Jr. MemberActivity: 45Merit: 3 Re: [ANN][Datacoin - DTC]2017 New Clients, New Developers October 18, 2017, 08:13:49 AM #162 Team, I just noticed a limitation with datacoin and Apertus.io. the version I am using v0.1.2.0dtc-hp11-unk-beta does not support the importaddress RPC call that was introduced with bitcoin 0.10.x because of this datacoin will not support several of the Apertus.io social media like functions that other blockchains are able to use.

the importaddress call is used to implement hash tag keywords, Proof of ownership searching, following profiles and decentralized voting. none of these features will work properly on datacoin unless the importaddress RPC call is implemented. my previous comments about starting a #rDatacoin thread on datacoin is not possible at this time. you can still use the #rDatacoin keyword and other keywords in your etching but nobody will be able to search for them unless importaddress() is supported.



Thanks for your time.

embii

dtc2017



Offline



Activity: 81

Merit: 16







MemberActivity: 81Merit: 16 Re: [ANN][Datacoin - DTC]2017 New Clients, New Developers October 18, 2017, 10:36:02 AM #164 Quote from: Robin37s on October 18, 2017, 09:40:25 AM it will be great if there are more exchanges for dtc



Datacoin was approved to be listed on HitBTC, it was frightfully expensive so we didn't proceed

We are on a maby list at Kraken

There is currently an application in with Bit-Z

Recently I have sent out applications to a few Japanese/Korean exchanges, not expecting a reply back for awhile

considering how busy they are with influx of new users.



Active development will get Datacoin on the exchanges, sure you can buy your way in but it's only a matter of time before

your coin is on that delisting/low volume notice.









Datacoin was approved to be listed on HitBTC, it was frightfully expensive so we didn't proceedWe are on a maby list at KrakenThere is currently an application in with Bit-ZRecently I have sent out applications to a few Japanese/Korean exchanges, not expecting a reply back for awhileconsidering how busy they are with influx of new users.Active development will get Datacoin on the exchanges, sure you can buy your way in but it's only a matter of time beforeyour coin is on that delisting/low volume notice.

extro24



Offline



Activity: 481

Merit: 252







Sr. MemberActivity: 481Merit: 252 Re: [ANN][Datacoin - DTC]2017 New Clients, New Developers October 18, 2017, 01:16:36 PM #165 Quote from: embii on October 18, 2017, 08:13:49 AM Team, I just noticed a limitation with datacoin and Apertus.io. the version I am using v0.1.2.0dtc-hp11-unk-beta does not support the importaddress RPC call that was introduced with bitcoin 0.10.x because of this datacoin will not support several of the Apertus.io social media like functions that other blockchains are able to use.

the importaddress call is used to implement hash tag keywords, Proof of ownership searching, following profiles and decentralized voting. none of these features will work properly on datacoin unless the importaddress RPC call is implemented. my previous comments about starting a #rDatacoin thread on datacoin is not possible at this time. you can still use the #rDatacoin keyword and other keywords in your etching but nobody will be able to search for them unless importaddress() is supported.



Thanks for your time.

embii



This is critical. Currently we are testing Datacoin 0.8.6 and will upgrade to 0.10.x in time.



-extro This is critical. Currently we are testing Datacoin 0.8.6 and will upgrade to 0.10.x in time.-extro Twitter: www.twitter.com/DatacoinX

embii



Offline



Activity: 45

Merit: 3







Jr. MemberActivity: 45Merit: 3 Re: [ANN][Datacoin - DTC]2017 New Clients, New Developers October 20, 2017, 02:58:49 AM #170 [APERTUS UPDATE]



Good news! HugPuddle.org is currently testing a fix for the bug that was preventing it from rebuilding variable storage etchings stored in a remote wallet.

We will be testing it's functionality soon by archiving a message in a wallet located in Moorhead MN and rebuilding the message via transaction ID in a remote wallet located in Long Beach CA. if it works as expected we will release the fix in v0.3.12-beta and make it available for download at Apertus.io shortly.



PS: If you are experimenting with DTC-V (Datacoin Variable Storage) you may begin to see your etchings show up on the bitfossil.org real time indexer later in the evening as we deploy the fix.



Thanks for your time.

AtomSea



Offline



Activity: 143

Merit: 100





So sexy, it hurts.







Full MemberActivity: 143Merit: 100So sexy, it hurts. Re: [ANN][Datacoin - DTC]2017 New Clients, New Developers October 20, 2017, 04:58:43 AM #171 Quote from: embii on October 20, 2017, 02:58:49 AM [APERTUS UPDATE]



Good news! HugPuddle.org is currently testing a fix for the bug that was preventing it from rebuilding variable storage etchings stored in a remote wallet.

We will be testing it's functionality soon by archiving a message in a wallet located in Moorhead MN and rebuilding the message via transaction ID in a remote wallet located in Long Beach CA. if it works as expected we will release the fix in v0.3.12-beta and make it available for download at Apertus.io shortly.



PS: If you are experimenting with DTC-V (Datacoin Variable Storage) you may begin to see your etchings show up on the bitfossil.org real time indexer later in the evening as we deploy the fix.



Thanks for your time.



Hi Team,



Tests successful:



"One small step for a block... one giant leap for blockchain"

http://bitfossil.org/8587d9f36e8d62202147921a8f0039a9bbcdd75abc11d2b797cf4ce307e8397c/index.htm



"Datacoin native field etch test on a non HugPuddle network machine to see if a HugPuddle networked machine pics up the Datacoin native field etching"

http://bitfossil.org/2a9e4d8c76a5fed92e3f9c6de7aec98a273751cb9c0dd6b71d385cbe3cd9bd38/index.htm



Native Datacoin variable field in full usage by Apertus, and completely viewable on bitFossil.org



Onwards and upwards.



The AtomSea



Hi Team,Tests successful:"One small step for a block... one giant leap for blockchain""Datacoin native field etch test on a non HugPuddle network machine to see if a HugPuddle networked machine pics up the Datacoin native field etching"Native Datacoin variable field in full usage by Apertus, and completely viewable on bitFossil.orgOnwards and upwards.The AtomSea

Chicago



Offline



Activity: 576

Merit: 259







Sr. MemberActivity: 576Merit: 259 Re: [ANN][Datacoin - DTC]2017 New Clients, New Developers October 20, 2017, 09:40:50 AM #174 Quote from: gjhiggins on October 20, 2017, 09:22:07 AM There were some GUI infelicities which do seem to have been addressed in this commit for Dogecoin (Core 0.9, I think) - https://github.com/dogecoin/dogecoin/commit/5ca5fb179e3ac873c9fe547b6bac68bdab87c0c7



Hi Graham,



It didn't go so well on my first pass either.

Maybe if we omit any of the src/qt{/*.cpp, /*.h} changes and just shunt it into the RPC core?



It got derailed from an easy integration while looking at the src/qt/walletmodel.cpp changes and ours has no WalletModel::getOutputs to patch.



Best Regards,

-Chicago Hi Graham,It didn't go so well on my first pass either.Maybe if we omit any of the src/qt{/*.cpp, /*.h} changes and just shunt it into the RPC core?It got derailed from an easy integration while looking at the src/qt/walletmodel.cpp changes and ours has no WalletModel::getOutputs to patch.Best Regards,-Chicago

gjhiggins



Offline



Activity: 1946

Merit: 1134









LegendaryActivity: 1946Merit: 1134 Re: [ANN][Datacoin - DTC]2017 New Clients, New Developers October 20, 2017, 11:02:06 AM #175 Quote from: Chicago on October 20, 2017, 09:40:50 AM Maybe if we omit any of the src/qt{/*.cpp, /*.h} changes and just shunt it into the RPC core?



That might work but I have a nasty suspicion that watch-address txs will still turn up in the GUI unless explicitly filtered out. It did actually work for Slimcoin but I absent-mindedly imported Slimcoin's burn address and that promptly brought the client to a standstill while it futilely calculated the staking weight of 000s of txs for which it didn't have a privkey, sigh. There was an earlier PR (



Cheers



Graham

That might work but I have a nasty suspicion that watch-address txs will still turn up in the GUI unless explicitly filtered out. Itactually work for Slimcoin but I absent-mindedly imported Slimcoin's burn address and that promptly brought the client to a standstill while it futilely calculated the staking weight of 000s of txs for which it didn't have a privkey, sigh. There was an earlier PR ( https://github.com/bitcoin/bitcoin/pull/2861 ) for the same feature, I found the discussion quite illuminating - the inclusion of pubkey-only addresses also has implications for a buncha other RPC commands and whilst the current focus is on Apertus' specialised and limited use case, in other broader use-case contexts, consequences for users need to be understood in detail - such as importing an address (pubkey) and subsequently, at a later date, importing the corresponding privkey and then (not unreasonably) expecting to be able to spend from what was previously a watch-only address but is now expected to be an ordinary address.CheersGraham