Bitcoin Forum
April 20, 2024, 02:08:53 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Altcoin Discussion / Bitcoin SV Excessive Blockchain Size on: September 28, 2021, 03:15:47 AM
Does anybody have any insight re: what's up with Bitcoin SV?

On the first of August, 2021, the block size was about 450GB.  Since then, it has more than doubled
to over 1160 GB as of the time of writing.  Many of the blocks are over 1GB and some are close to 2GB.
This explosion in size is swamping my ability/willingness to throw endless computing resources
into supporting this otherwise worthless coin.  Nevertheless, I am still curious re: wtf?

IMHO, there is no way this is any kind of organic explosion in new adoption and is instead some
sort of scam/attack.  My guesses are:

1. This bloat comes from a mass of fake and needlessly complicated transactions that are
intended to draw attention to this coin.  For people who don't see the gory details, this explosion
of activity might look like an explosion in new popularity/adoption, so therefore this must be
the _next great coin_ to get involved with.

2. Perhaps this is a denial-of-service attack? Is somebody just generating endless quantities of large and complex transactions in order to bloat the blockchain, push the little people out, and generally wreak chaos and havoc for this poor hapless coin?


It has occurred to me to consult the GrandGoogle about this but all I find is ra-ra apparently
written by the same group of people.  I don't actually find any real documentation or discussion.
Obviously my failing to find this, but hopefully somebody here can clue me in.  Thanks.
2  Economy / Trading Discussion / Introducing Bookwerx. Bookkeeping for traders. on: November 03, 2019, 12:57:07 AM
Hello Folks,

One element of trading that's particularly nettle-some is doing bookkeeping.  Believe it or not, many people simply ignore the issue and don't even bother.  Many people try to cobble together spreadsheets and enter transactions by hand.  Neither of these choices are particularly scaleable.  I for one would hate to unleash the TraderBot and then try to follow behind entering transactions by hand in its wake. But creating stronger software that does a better job, is, as with most things computing, easier said than done.

But fear not. All is not lost.  That light in the tunnel is not really an on-rushing train.  I'd like to announce the bookwerx multi-currency, client-server, bookkeeping system.  This is a simple and easy to get started with, open source project, complete with functioning public API.  Take it for a spin around the block, and if it seems useful to you, it's easy enough to setup your own private installation.

bookwerx-core-rust (https://github.com/bostontrader/bookwerx-core-rust) Is the meat and potatoes of bookwerx.  This is a server, written in Rust, that implements an API for doing bookkeeping.  With this API you can define the currencies and accounts that you wish to use, create suitable transactions, observe aggregate phenomenon via reporting tools, and hunt down nettle-some bits o' lint with the linter.

bookwerx-ui-elm (https://github.com/bostontrader/bookwerx-ui-elm) Is an example user interface the enables the user to manually do bookkeeping.  An important benefit of this help the user understand the bookwerx-core-rust API.  With this app the user can observe the http traffic between the UI and the server.  In this way perhaps insight can be had.


Public Demonstration Server

We have a public demonstration server available at http://23.253.160.60.  This will serve bookwerx-ui-elm.  So it's easy enough to get your feet wet with manual bookkeeping, learn the server's API by observing the http traffic to and fro, and eventually graduate to an automated connection to the server, using the API.

3  Bitcoin / Project Development / Bookwerx- The Multicurrency Bookkeeping API on: November 01, 2019, 12:40:23 AM
Hello Folks,

We hereby announce the bookwerx multi-currency, client-server, bookkeeping system.

bookwerx-core-rust (https://github.com/bostontrader/bookwerx-core-rust) Is the meat and potatoes of bookwerx.  This is a server, written in Rust, that implements an API for doing bookkeeping.  With this API you can define the currencies and accounts that you wish to use, create suitable transactions, observe aggregate phenomenon via reporting tools, and hunt down nettle-some bits o' lint with the linter.

bookwerx-ui-elm (https://github.com/bostontrader/bookwerx-ui-elm) Is an example user interface, the primary purpose of which is to help the user understand the bookwerx-core-rust API.  With this app the user can observe the http traffic between the UI and the server.  In this way perhaps insight can be had.


Public Demonstration Server

We have a public demonstration server available at http://23.253.160.60.  This will serve bookwerx-ui-elm.  From there, work the app, observe the http traffic with the server, and gain personal edification.


Why?

As you might have experienced, doing bookkeeping for your crypto-empire is considered by some authorities to be the most tedious and boring thing there is.  Typing this stuff into your spreadsheet by hand is absurdly labor-intensive and error-prone.  But building stronger software to manage this better is a monstrous distraction from your primary goal of global conquest. Although none of this task is particularly rocket sciency, the individual pieces of it work well together to collectively put up quite a defence.  Instead of wasting your time reinventing this wheel, why not let bookwerx do the dirty work for you?

Consider your own personal experience with mining pools and crypto-exchanges.  As a user I want to know what my balances are.  I want to be able to see all the transactions that created said balances and I'd like to see running totals to assist in debuggery.  I do not want to see random fragments of this information scattered all over the website, complete with blind-spots, nor do I want to see numbers asserted as correct without any derivation, or lists of transactions with many currencies mixed together and no running totals.

Use cases:

  • I'm doing automated trading.  Where are all my coins _right now_ ?
  • My mining pool creates a blizzard of transactions.  My users want to know what they have earned, what they have received, and how much they are due now.  I want a managerial accounting overview of the entire process.
  • My MtGox killer crypto-exchange is almost ready to go. The setting sun reminds me that it's time to strap on a hastily built bookkeeping system, just in time for tomorrow morning's debut.  My market supports 500 different coins and my customer funds are divided into 8 different locations.  Those pesky customers want to know and verify all their balances.   For extra credit: Realize that users of valuable coins don't like round-off error and that it annoys them to wonder if the discrepancies that are ubiquitous in my market's UI vs the customer's internal records are ordinary errors, round-off errors, theft, merely round-off-for-display issues or perhaps some new form of hitherto-now unknown form of dumfoolery.

Multi-Currenciarity

What exactly do this mean?  In conventional bookkeeping the sum of the Debits of a transaction should equal the sum of the Credits.  Bookwerx merely drops that constraint.  The actual software plumbing of creating accounts, transactions, etc, remains essentially the same.

The DR=CR constraint in conventional bookkeeping works just fine when dealing with a single currency.  The value in doing this is that a handful of conditions hold true such as Assets = Liabilities + Equity, or that Net Income = Revenue - Expenses.  It also serves as a simple error detection scheme when creating transactions.  However, the conventional system requires unpleasant contortions to try to squeeze in other currencies.  It's bad enough when you try to work with just a few multi-currency transactions, but the scheme completely disintegrates when you push harder.

bookwerx simply drops this constraint.  The sun still rises by command of the rooster.

With our new found freedom we can create transactions such as:

DR   Cash in Mattress   500      Quatloos
CR   Bank of Mises      15      General Atomic Shekles

What does this mean?  By inspection it looks like a currency exchange and a bank withdrawal.  The quantity of value withdrawn from the bank really does equal the quantity stuffed into the mattress, even if the actual numbers and units are different.

The loss of DR=CR as an error detection scheme for transactions is a minor price to pay.  Fortunately, other error detection mechanisms exist, such as reconcile your balances.

The biggest issues comes from wrapping our heads around the meaning of financial reporting.  Balance Sheet and Profit and Loss Statements work as usual, but it's not at all obvious how to "compare" things.

For example:


Assets:                   Dec 31, 2019      Dec 31, 2018
    Cash in Mattress           500 QTL           200 QTL
    Bank of Mises              250 GAS           550 GAS
                           -------           -------
                  subtotal     Huh                Huh

Liabilities:
    Wecheatembad Credit Corp   500 BTC           150 BTC

Equity
    Owner's Equity           10000 CNY         10000 CNY   


In this example, assets really do still equal the sum of liabilities and equity, even if there's an exchange rate issue to befuddle the analysis.  Is the 2019 BS "better" than the 2018 edition?

The bottom line here is that the actual plumbing of bookkeeping does not require the DR=CR constraint and it works just fine without.  However the analysis of the meaning of transactions and reports is a topic beyond the scope of mere bookkeeping.  This distinction is hidden when only using a single currency, but is unfortunately not magically solved with bookwerx 1.0

But while you ponder the meaning of these deep questions, you'll still want to know the actual bookkeeping details of these things on a day-to-day basis.
4  Alternate cryptocurrencies / Altcoin Discussion / [Ann] Studcoin on: December 03, 2017, 12:51:17 AM
Hello Folks,

I'd like to find some other developers who want to study and learn more about cryptocoins.

I have many years of experience with all sorts of software development and programming languages generally, and have been a cryptocoin enthusiast since 2011, so I have a modest bit of capacity to bring to the table.

Imagine trying to implement a new coin.  What _specific_ steps would you go through?  The goal of this project is not primarily to create yet another worthless s**t coin, but instead, to learn more about the inner workings of these things. This is a hobby project for personal edification.  If you need to become a billionaire by next Friday in order to make rent, you're wasting your time reading this. Nevertheless, for purposes of concreteness I'll call this "student coin" or studcoin for short. I'm particularly I'm _not interested_ in merely cloning and building existing software.  Instead I want to ...

1. Determine a "good" method of creating the coins.  Discuss the pros 'n' cons of POW vs. POS.  How to maybe start with POW and ease into POS.  What other algorithms are out there?

2. Determine whether or not the existing standard Bitcoin style block-chain model is even worth further contemplation or are there newer models such as Ethereum that would be better to focus on?

3. Find examples of existing software that already exist for dissection and study.

4. Establish a github account to host probably more than one repo from this project. 

4.1  Perhaps there's a repo for the command line stuff (studcoind, studcoin-cli etc.)

4.2  And another for studcoin-qt.  Do we even want to use QT?  What other alternatives are there?

4.3  And another for a block-chain explorer.

4.4  And perhaps another for a mining pool.

4.5  Vanity address generator?

For each repo I'd like to start with a fresh project and then start carefully copying in pieces of code found from other places and/or created from scratch.  I _don't_ want to just fork existing software, I would instead like to examine the piece involved, cherry pick the good ones, and assemble a quality build process.

Although this is not a path to easy money, I expect you'll gain some value in participation.

Thanks in advance for your consideration.

Dr Mutz



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!