Information processing system, information processing method, and computer program

Abstract

Provided are an information processing system, an information processing method, and a computer program that allow setting control to be easily performed for a paywall by using a blockchain technology. The information processing system comprises: a server device that receives content creation and editing; a first client device for a content poster; a second client device for a content viewer; and a blockchain system. The first client device embeds the script of a paywall in an arbitrary portion of created content. In accordance with the script, the smart contract of the blockchain system performs the process for cost payment from the wallet address of the viewer to the wallet address of the poster. When the record of success in the process for payment performed by the smart contract has been confirmed, the server device transmits data on the content of interest after the cancellation of the paywall to the second client device.

Description

Information processing system, information processing method, and computer program

[0001] The present invention relates to an information processing system, an information processing method, and a computer program for controlling a paywall for text on the Web.

[0002] A paywall system is used in which some or all of articles or blogs published on the web are kept private from anyone other than regular subscribers or readers who have temporarily paid, and revenue can be collected for the content published on the web (see, for example, Patent Document 1).

[0003] Regarding the data for paid portions of articles and blogs, one method is for the article or blog platform itself or other operators to register the content in a separate database, and readers can purchase it from the platform or operator server.

[0004] JP 2014-154143 A

[0005] When platform providers or operators that store content sell paid content, they must also manage that paid content in a database to prevent leaks. Furthermore, they must also collect purchase funds from readers and make payments to article and blog contributors, raising concerns that security risks may be spread across multiple locations. In order to store content, blog and article contributors must register as contributors to the paywall function with the platform provider or other operators, which can be a hassle.

[0006] The present invention aims to provide an information processing system, an information processing method, and a computer program that enable easy setting and control of a paywall using blockchain technology.

[0007] An information processing system according to one embodiment of the present disclosure includes a server device that provides a web application that accepts the creation and editing of content and distributes the created content, a first client device of a content contributor who uses the web application, a second client device of a viewer of content distributed from the server device, and a blockchain system connected to the server device and the second client device, wherein the first client device embeds a paywall script in any location of the content to be created, and when the second client device requests the removal of the paywall for the target content, a smart contract of the blockchain system executes a cost payment process from the viewer's wallet address to the contributor's wallet address using the script, and when the server device confirms a record of the successful payment process in the smart contract, it transmits data of the target content after the paywall has been removed to the second client device.

[0008] In the information processing system, information processing method, and computer program disclosed herein, when the paywall is removed, a script that causes a smart contract to execute a cost payment process from the viewer's wallet address to the poster's wallet address can be embedded at any location in the content.

[0009] According to the present disclosure, it is possible to control the setting of paywalls using blockchain technology.

[0010] 1 is a schematic diagram of an information processing system of the present disclosure. FIG. 1 is a block diagram showing the configuration of a first client device. FIG. 2 is a block diagram showing the configuration of a second client device. FIG. 3 is a block diagram showing the configuration of a server device. FIG. 4 is a block diagram showing the configuration of a node in a blockchain system. FIG. 5 is a flowchart showing an example of a paywall setting procedure. FIG. 6 is a diagram showing an example of a display of a paywall reception interface. FIG. 7 is a diagram showing an example of a paywall display. FIG. 8 is a flowchart showing an example of a paywall removal procedure. FIG. 9 is a flowchart showing an example of a paywall removal procedure. FIG. 10 is a flowchart showing an example of a paywall removal procedure.

[0011] The present disclosure will be specifically described with reference to the drawings showing embodiments thereof.

[0012] In this disclosure, a "blockchain system" refers to a system that includes multiple computers that can communicate with each other and a network that connects the multiple computers, and creates a blockchain through distributed processing of the multiple computers. Required transactions are executed and the results are captured in the blockchain.

[0013] 1 is a schematic diagram of an information processing system 100 according to the present disclosure. The information processing system 100 includes a first client device 1, a second client device 2, a server device 3, and a blockchain system 4. The first client device 1, the second client device 2, and the server device 3 can transmit and receive data to and from each other via a network N, which is the so-called Internet. The first client device 1, the second client device 2, and the server device 3 are each associated with a wallet address in the blockchain system 4. Private keys for accessing the wallet addresses are managed individually by users or operators of the first client device 1, the second client device 2, and the server device 3.

[0014] The information processing system 100 is based on a content distribution service in which a server device 3 stores web content, including text, images, video, or audio, posted by a first client device 1 in a content database (DB) 310, and provides the web content in response to a request from a second client device 2. The web content may be a blog, a news site, or a corporate public relations page.

[0015] Paywall control in the information processing system 100 of the present disclosure is realized as an additional function for this content distribution service by a plug-in program P1 that writes a control script for part or all of the web content from the first client device 1, and a smart contract (paywall removal contract) 400 deployed in the blockchain system 4. The script embedded in the web content by the plug-in program P1 indicates the paywall to viewers of the web content (site visitors) and causes the second client device 2, the server device 3, and the smart contract 400 to each execute procedures for removing the paywall.

[0016] Here, to use the plug-in program P1, neither the user of the first client device 1 (the contributor of the web content) nor the user of the second client device 2 (the viewer of the web content) is required to register as a user for the system. Furthermore, in the information processing system 100 disclosed herein, assets (such as legal tender or crypto assets) from viewers using the second client device 2 who request paywall removal are held by neither the administrator of the server device 3 nor the smart contract 400. The smart contract 400 collects a fee for the payment of assets from viewers to contributors for paywall removal, but does not hold the assets from viewers and then pay them to the contributor. The smart contract 400 records and makes available for reference that the second client device 2 has paid the assets for paywall removal to the first client device 1.

[0017] In this way, the configuration and processing procedure of the information processing system 100 for realizing the setting or removal of a paywall using blockchain technology by the plug-in program P1 will be described.

[0018] FIG. 2 is a block diagram showing the configuration of the first client device 1, and FIG. 3 is a block diagram showing the configuration of the second client device 2. Both the first client device 1 and the second client device 2 are desktop or laptop personal computers (PCs). The first client device 1 and the second client device 2 may also be smartphones, tablet terminals, etc. The first client device 1 will be described below. The second client device 2 will be assigned a reference numeral corresponding to the configuration of the first client device 1, and a detailed description thereof will be omitted.

[0019] The hardware configurations of the first client device 1 and the second client device 2 are the same as shown in Figures 2 and 3, and which one is which is switched depending on the position (account) in the content distribution service. A web application for creating and editing web content requires account registration to identify the poster, and when the user logs in to the web application with that account and applies the plug-in program P1, the general-purpose computer functions as the first client device 1. A computer that acquires web content for viewing functions as the second client device 2.

[0020] The first client device 1 includes a processing unit 10, a storage unit 11, a communication unit 12, a display unit 13, and an operation unit 14. The processing unit 10 includes one or more processors such as a central processing unit (CPU), a micro-processing unit (MPU), or a graphics processing unit (GPU). The processing unit 10 includes a memory that is a temporary storage medium such as a static random access memory (SRAM) or a dynamic random access memory (DRAM). The processing unit 10 may be configured as a single piece of hardware (SoC: System On a Chip) that integrates the processor, the memory, the storage unit 11, and the communication unit 12.

[0021] The memory unit 11 is a relatively large-capacity non-temporary storage medium such as a hard disk or flash memory. It stores programs (program products) necessary for the processing unit 10 to execute processing, as well as reference configuration data. The program products include an operating system (OS) program, a web browser program P0 running on the OS, and a plug-in program P1 for the web browser program P0. The plug-in program P1 is data identifying the functions of the present disclosure added to the web browser program P0, and is temporarily stored in the memory of the processing unit 10 by the function of the web browser program P0. The program product may also include a special client program that replaces the web browser program P0 and the plug-in program P1 and performs those functions. The memory unit 11 may also store the wallet address of the user using the first client device 1.

[0022] The program product including the web browser program P0 and plug-in program P1 stored in the storage unit 11, or a specific client program replacing them, may be a program group (web browser program P90 and plug-in program P91) stored in a computer-readable non-transitory storage medium 9 that is read by the processing unit 10 and stored in the storage unit 11. The program product stored in the storage unit 11 may be a program product that the processing unit 10 downloads from a download server via the communication unit 12 and stores in the storage unit 11.

[0023] The communication unit 12 is a communication device that realizes communication via the network N. The communication unit 12 may be any of a network card for a wired LAN, a communication device that realizes carrier communication via a carrier network, an optical communication device, and a communication device compatible with a wireless network such as Wi-Fi or Bluetooth (registered trademark). The communication unit 12 may be capable of transmitting and receiving data of a web application provided by the server device 3 and performing TCP (Transmission Control Protocol) communication for transmitting and receiving content.

[0024] The display unit 13 uses a display such as a liquid crystal display or an organic EL (Electro Luminescence) display. The display unit 13 displays a web page including text and images through processing by the processing unit 10. The display unit 13 may use a display with a built-in touch panel.

[0025] The operation unit 14 is a user interface such as a keyboard or a pointing device that accepts operations from the user. The operation unit 14 may be a touch panel built into the display of the display unit 13, or may be physical buttons. The operation unit 14 may be a voice input unit that accepts operations by voice using a voice recognition function. The operation unit 14 can notify the processing unit 10 of operation information by the user.

[0026] 4 is a block diagram showing the configuration of the server device 3. For simplicity, the following description will be given assuming that the server device 3 is configured as a single server computer, but the server device 3 is configured to distribute processing across multiple server computers. The server device 3 is managed by a content distribution service provider. The server device 3 includes a processing unit 30, a storage unit 31, and a communication unit 32.

[0027] The processing unit 30 includes one or more processors such as a CPU, an MPU, a GPU, etc. The processing unit 30 includes a memory that is a temporary storage medium such as an SRAM or a DRAM.

[0028] The memory unit 31 is a relatively large-capacity non-transitory storage medium such as a hard disk or flash memory. The memory unit 31 stores data referenced by the processing unit 30. A wallet address for the system of the present disclosure, assigned to a content distribution service provider managing the server device 3, is registered in the memory unit 31. This wallet address is an address usable in the blockchain system 4, is used exclusively for signatures, and is not linked to assets such as crypto assets. A content DB 310 is constructed in the memory unit 31 and stores posted web content in association with user information (account) of a poster who is a user of the first client device 1. The content DB 310 stores web content (also referred to as posts, articles, or web pages) received by a content creation / editing web application provided by the server device 3 in association with a web content identifier, an account (the poster's website domain), and a posting ID. For each poster's account, the content DB 310 stores data for the poster to receive cryptocurrency when the paywall is removed, such as the poster's wallet address and the cryptocurrency network, as well as currency unit settings, as poster information.

[0029] The communication unit 32 is a communication device that realizes communication via the network N. The communication unit 32 is not limited to a specific embodiment as long as it can communicate with a communication device such as the first client device 1.

[0030] 5 is a block diagram showing the configuration of a node 40 in a blockchain system 400. The node 40 may be a server computer, a desktop or laptop PC, or a communication terminal device such as a smartphone or tablet terminal. The node 40 includes a processing unit 41, a storage unit 42, and a communication unit 43. Furthermore, as long as the node 40 is a device that includes at least the processing unit 41 and the communication unit 43, part or all of the node can be configured by a part of the processing unit 41.

[0031] The processing unit 41 uses a processor such as a CPU or GPU, a memory, etc. The processing unit 41 may be configured as a single piece of hardware that integrates a processor, a memory, a storage unit 42, and a communication unit 43. The memory of the processing unit 41 may store a private key that is unique to each node 40. The processing unit 41 then executes each process based on the node program stored in the storage unit 42, causing the general-purpose computer to function as a node in the blockchain system 400.

[0032] The storage unit 42 uses a hard disk or flash memory and stores programs and data referenced by the processing unit 41, including the node program. The storage unit 42 stores the blocks that make up the blockchain. The node program includes a program P4 for functioning as a smart contract (the processing unit 41 that executes predetermined calculation processing for requests) 400, which will be described later. The storage unit 42 may also store a public key and an address based on a private key.

[0033] The communication unit 43 is a communication module that realizes intercommunication between the nodes 40. The communication unit 43 uses a network card, an optical communication device, a wireless communication device, or the like.

[0034] The process of setting and releasing a paywall by the plug-in program P1 and the smart contract 400 in the information processing system 100 configured as above will be described below.

[0035] First, a content contributor, who is a user of the first client device 1, creates web content via a web application for creating and editing content provided by the server device 3. If the plug-in program P1 of the present disclosure is applied to the contributor's account in the web application provided by the server device 3, it is possible to set a paywall that can be removed by payment, as described below.

[0036] 6 is a flowchart showing an example of a paywall setting procedure. Based on the web browser program and the plug-in program P1, an editing page for web content provided by the server device 3 is displayed, and the processing unit 10 of the first client device 1 executes the following process until an end operation is performed.

[0037] The processing unit 10 accepts an edit or save operation on the displayed edit page (step S101). The processing unit 10 determines whether embedding of a paywall provided by the plug-in program P1 has been selected for the web content to be edited (step S102). The edit page can accept edits such as inserting text or images for each edit unit within the web content, and can call tools that accept external service linkage functions, etc. When the plug-in program P1 is applied, a paywall that links with the smart contract 400 can be set within the web content as one of the tools.

[0038] If it is determined in step S102 that embedding of a paywall has not been selected (S102: NO), the processing unit 10 returns the process to step S101 and continues the operation reception process until an end operation is performed on the editing page.

[0039] If it is determined in step S102 that embedding a paywall is selected (S102: YES), the processing unit 10 embeds a paywall script in the specified location of the web content using the plug-in program P1 (step S103), and displays an interface for accepting selection of the price and currency unit on the editing page (step S104). The script in step S103 includes code for displaying an interface including a link to activate linking to the wallet when viewed, and specifies identification data for calling the smart contract 400, etc. In step S104, the processing unit 10 may also accept settings for affiliate rewards.

[0040] The processing unit 10 saves the price accepted through the reception interface displayed in step S104 and the data of the selected currency unit in the embedded script (step S105). In step S105, the processing unit 10 stores the price and the data of the selected currency unit in metadata in the private web content as script parameters. If the price has already been accepted through the reception interface, the processing of S105 may be omitted.

[0041] The processing unit 10 determines whether or not publication (posting) of the web content to be edited has been selected (step S106). If publication has not been selected (S106: NO), the processing unit 10 transmits the web content data to the server device 3 in a private state (step S107). This allows the server device 3 to store the web content in the content DB 310. The processing unit 10 returns the process to step S101 and continues accepting operations until an end operation is performed on the page.

[0042] If publishing of web content for which embedding of a paywall is selected is selected (S106: YES), the processing unit 10 creates setting data for the paywall (paywall setting data) (step S108). The paywall setting data created in step S108 includes the creation date and time, the publication date and time, or the update date and time, an identifier using a universally unique lexicographically sortable identifier (ULID) for the post, a post ID within the content distribution service, the price and currency unit written and stored in step S105, and affiliate fee settings. The paywall setting data is written in the web content as a parameter of the paywall script embedded in the web content. The paywall setting data itself can be inserted at any time during editing of the web content, and step S108 may simply update the publication date and time. The paywall setting data may be transmitted to the server device 3 as separate data identifiable for each paywall.

[0043] The processing unit 10 transmits the data of the web content in a public state to the server device 3 (step S109), thereby causing the server device 3 to store the web content in the content DB 310. The processing unit 10 then terminates the paywall setting process for the public web content. Before or after step S109, the processing unit 10 may again transmit the paywall setting data created in step S108 to the server device 3.

[0044] Through the process of FIG. 6, the content DB 310 of the server device 3 stores the Web content including the paywall setting data in association with the poster's user information (account or domain) and the posting ID.

[0045] FIG. 7 is a diagram showing an example of the display of a paywall reception interface. FIG. 7 shows a web browser screen 130 displayed on the display unit 13 of the first client device 1. The web browser screen 130 in FIG. 7 shows an edit page 131 of the web content to be posted. A reception interface 132 is displayed on the edit page 131 when embedding a paywall in the section being edited is selected. The reception interface 132 includes an input field 133 for inputting numbers, a pull-down menu 134 for selecting a currency unit, and an update button 135. In the reception interface 132 in FIG. 7, 1000 yen is set as the legal tender. When the update button 135 is selected by the operation unit 14, the processing unit 10 executes the entry of the price and currency unit data received in S105 described above. In the example of FIG. 7, Ether (ETH) is selected as the currency unit, and a numerical value is input.

[0046] 7 includes a public interface 136. When the public interface 136 is selected, paywall setting data including the price and currency unit data selected in the reception interface 132 is created (S108), and the posted content to be edited becomes public.

[0047] Second, a process for viewing web content with an embedded paywall and disabling the paywall as described above will be described. FIG. 8 is a diagram illustrating an example of a paywall display. FIG. 8 illustrates a web browser screen 230 displayed on the display unit 23 of the second client device 2 of a web content viewer. The web browser screen 230 in FIG. 8 displays posted web content, and a paywall interface 231 is displayed by an embedded script after the "Read more" mark. The interface 231 in FIG. 8 displays the price of the web content read by the web browser program P0 based on the paywall setting data described in the web content (or referenced from the content DB 310). The paywall setting data includes a posting ID that identifies the web content being displayed in the web browser program P0, the price, the currency unit, etc. The interface 231 displays a button 232 linked to a link that activates linking to the viewer's user wallet by the script.

[0048] The following describes the processing that occurs when the button 232 in the web content displayed on the web browser screen 230 shown in Fig. 8 is selected by the operation unit 24. Figs. 9 to 11 are flowcharts showing an example of the procedure for removing the paywall.

[0049] When an operation indicating an intention to disable the paywall (here, selection of button 232) is received (step S201), the processing unit 20 launches the viewer's user wallet application based on the paywall script embedded in the web content and the web browser program P0 (step S202). The wallet application is a plug-in program applied to the web browser program P0 of the second client device 2. The wallet application may be launched as a separate application.

[0050] The processing unit 20 acquires the wallet address of the wallet application that has been launched based on the script (step S203). If the processing unit 20 fails to launch the wallet application in step S203, it does not continue the subsequent processing. In this case, the viewer using the second client device 2 cannot disable the paywall.

[0051] The processing unit 20 accepts the selection of the cryptocurrency distribution network and currency unit that can be used for payment from the acquired wallet address (step S204). In step S204, the processing unit 20 may acquire the cryptocurrency network and currency unit that can be used for payment set in the contributor information of the contributor of the target web content using a script included in the web content, and accept the selection operation from there.

[0052] The processing unit 20 accepts a purchase operation from an interface displayed by a script included in the Web content (step S205). When the purchase operation is accepted, the processing unit 20 transmits a request for information required to remove the paywall (purchase the content) to the server device 3 by using the script (step S206).

[0053] When the processing unit 30 of the server device 3 receives a request from the second client device 2 (step S301), it reads information necessary for the payment to remove the paywall from the poster information in the content DB 310 (step S302). The necessary information includes, for example, the poster's wallet address for receiving the payment, a signature used in the processing described later, and the like.

[0054] The processing unit 30 acquires the exchange rate between the price and currency unit of the paid portion of the target web content included in the paywall setting data and the network and currency unit of the cryptocurrency included in the paywall removal request at the time of receiving the request (step S303). The processing unit 30 calculates the payment amount in currency units of the cryptocurrency included in the paywall removal request (step S304).

[0055] The processing unit 30 acquires the ULID at that time and obtains it as the ticket ID (step S305). The data is not limited to the ULID, but may be any other data string as long as it includes a timestamp at that time and is a unique identification number that can be easily sorted.

[0056] The processing unit 30 creates a signature message that includes the issued ticket ID, the wallet address for receiving the ticket, the price, the currency unit, and the posting ID as character strings (step S306). If affiliate setting data is included, the processing unit 30 also includes this data.

[0057] The processing unit 30 signs the created signature message using the private key corresponding to the signature wallet address stored in the storage unit 31 (step 307). The processing unit 30 stores the identifier of the web content including time information, the data of the cryptocurrency to be paid, and the signature message as ticket information, in association with the ticket ID (step S308).

[0058] The processing unit 30 returns to the second client device 2 the information necessary to remove the paywall, such as the data read in step S301, the payment amount information calculated in step S303, the signature data, the receiving wallet address, and the ticket ID (step S309). The processing unit 30 may also include other information such as the signature wallet address. If affiliate setting data is included, this is also included.

[0059] The processing unit 20 of the second client device 2 receives the necessary information corresponding to the request (step S207).

[0060] Based on the received information, the processing unit 20 acquires identification data of the paywall removal smart contract 400 using the script of the web content (step S208). The identification data of the smart contract is included as metadata of the web content. Alternatively, the identification data may be acquired as necessary information from the server device 3.

[0061] The processing unit 20 calls the payment function of the smart contract 400 in the blockchain system 4 based on the identification data acquired in step S208 (step S209). The processing unit 20 provides the smart contract 400 with data such as the signature data, ticket ID, receiving wallet address, payment amount, and posting ID received as necessary information from the server device 3 (step S210). If affiliate setting data is included, the processing unit 20 also provides this.

[0062] The smart contract 400, using the called payment function, checks for inconsistencies in the data provided in step S210 (e.g., whether the affiliate is valid or invalid) and the expiration date obtained from the time information of the ticket ID (ULID) (step S401). As part of the check, the smart contract 400 creates a payment message containing the provided ticket ID, receiving wallet address, price, currency unit, and posting ID as strings (step S402). The smart contract 400 checks whether the created payment message corresponds to the signature message of the server device 3 based on the provided signature data (step S403). Since the message creation algorithm executed by the server device 3 matches the message creation algorithm executed by the smart contract 400, if the price or time has been tampered with, while the same message should be created, the check fails due to a mismatch. In step S403, the smart contract 400 may check for a match between the messages.

[0063] The smart contract 400 determines whether the checks in steps S401 and S403 were successful (step S404). If it is determined that the checks were unsuccessful (S404: NO), the smart contract 400 does not perform any further processing and returns an error to the call of the payment function (step S405).

[0064] The checks in steps S402 and S403 allow the authenticity of the posted content to be removed from the paywall to be checked using the post ID, and price tampering can be prevented by including the price. Including affiliate setting data in the checks also makes it possible to prevent tampering with affiliate commission rates.

[0065] If it is determined that the check was successful (S404: YES), the smart contract 400 transfers the amount of cryptocurrency corresponding to the payment amount from the viewer's wallet address to the poster's receiving wallet address via the smart contract (step S406). In step S406, the smart contract 400 collects a portion of the cryptocurrency paid by the viewer as a fee. If the viewer purchases web content via an affiliate, the smart contract 400 transfers a portion of the cryptocurrency paid by the viewer to the affiliate as a referral fee based on the affiliate settings set for the target content. In addition, the viewer is responsible for the gas costs for the processing of the smart contract 400 in steps S401-S406 and step S407 described below.

[0066] The smart contract 400 stores a record including the viewer's wallet address, an identifier containing time information at the time of posting, a post ID, and a ticket ID in the storage (storage unit 42) as evidence that the viewer has paid the cryptocurrency to remove the paywall for the target web content (step S407). The record includes, for example, a non-zero value using the viewer's wallet address and post ID as keys. These pieces of data are not required for the record, and the record may include other data as long as it can identify which viewer made a payment for which post.

[0067] After calling the payment function, the second client device 2 determines whether the check is successful and whether the crypto asset transfer transaction has been recorded (step S211). If the check is unsuccessful and it is determined that the transfer transaction has not been recorded (S211: NO), the processing unit 20 stops removing the paywall and ends the process.

[0068] If it is determined that the transfer transaction has been recorded (S211: YES), the processing unit 20 accepts a signature corresponding to the viewer's wallet address for the arbitrary character string (step S212). In step S212, for example, the processing unit 20 creates a signature based on the private key held by the wallet application launched in step S202. The processing unit 20 transmits the message and signature to the server device 3 using a script embedded in the content (step S213).

[0069] When the processing unit 30 of the server device 3 receives the signature via a script embedded in the web content being displayed on the second client device 2 (step S310), it queries the specified smart contract 400 for the signature (step S311). In step S311, the processing unit 30 queries whether the viewer has made a payment for the target post ID. For example, in step S311, the processing unit 30 specifies the viewer's wallet address, which can be calculated from the signature, and the post ID, and queries whether there has been a purchase (payment record) for removing the paywall for the target web content using the wallet address of the viewer who signed.

[0070] If the signature of the viewer's wallet address is valid, the smart contract 400 determines whether there is a record stored in step S407 with a non-zero value using the specified wallet address and post ID as keys. If the value is not zero, the smart contract responds that there is a record of a legitimate payment. In other words, processing between the server device 3 and the smart contract 400 confirms whether there is a memory indicating that the viewer who signed the signature has indeed made a payment to remove the paywall for the corresponding web content. Therefore, the smart contract 400 returns a confirmation result.

[0071] The processing unit 30 of the server device 3 determines whether or not a result indicating that there is a record of payment evidence from a viewer who has entered a valid signature has been returned in response to the inquiry (step S312).

[0072] If the processing unit 30 determines that the result returned indicates that there is no record of payment proof (S312: NO), it returns an error (step S313) and ends the process.

[0073] If the processing unit 30 determines that the result indicates that there is a record (S312: YES), it removes the paywall, reads the removed web content from the content DB 310, and sends it to the second client device 2 (step S314).

[0074] The processing unit 20 of the second client device 2 receives the result of the signature transmission in step S213 (step S214), displays a screen on the display unit 23 according to the result (step S215), and ends the process. In step S214, if the server device 3 successfully verifies the signature and determines that there is a payment record, the paywall-unlocked web content is displayed, and if there is no record, an error is displayed.

[0075] In this way, a removable paywall can be easily set by the poster using blockchain technology. When the paywall is removed, the server device 3 that distributes the content does not receive payment from the viewer, and there is no need to separately store the content outside the server device 3 as paid content.

[0076] The embodiments disclosed above are illustrative in all respects and are not restrictive. The scope of the present invention is defined by the claims, and includes all modifications within the meaning and scope of the claims.

[0077] REFERENCE SIGNS LIST 1 First client device 10 Processing unit 11 Storage unit P1 Plug-in program (computer program) 2 Second client device 20 Processing unit 3 Server device 30 Processing unit 4 Blockchain system 400 Smart contract (computer program)

Claims

1. An information processing system comprising: a server device that provides a web application that accepts the creation and editing of content and distributes the created content; a first client device of a content contributor that uses the web application; a second client device of a viewer of content distributed from the server device; and a blockchain system connected to the server device and the second client device, wherein the first client device embeds a paywall script in an arbitrary location in the content it creates, and when a request to remove the paywall for the target content is made by the second client device, a smart contract in the blockchain system executes a payment process for the cost from the viewer's wallet address to the contributor's wallet address using the script, and when the server device confirms a record of successful payment processing in the smart contract, it transmits data of the target content after the paywall has been removed to the second client device.

2. The information processing system described in claim 1, wherein when the second client device makes a request to remove the paywall, the server device creates a signature message including a string of characters that includes the post ID of the target content, the poster's wallet address, the price, and the currency unit of the cryptocurrency used for the payment, the server device creates a signature for the signature message based on the server device's wallet address, and the smart contract determines whether to execute the payment process by verifying the signature.

3. The information processing system of claim 1, wherein the server device stores ticket information including time information at the time the request to remove the paywall was made by the second client device, the post ID of the target content, and a ticket ID including time information at the time of issuance; the server device transmits the ticket ID to the second client device; the payment process is executed by specifying the ticket ID; if the payment process is successful, the smart contract stores a record including the wallet address of the viewer making the payment and the post ID of the payment target; and the server device confirms the success record based on the confirmation result of the record in the smart contract that specifies the post ID of the target content and the wallet address of the viewer.

4. The information processing system of claim 1, wherein the script causes the second client device to launch the viewer's wallet app and display an interface that accepts the specification of the currency unit of the cryptocurrency that can be paid using the wallet app; the script causes the server device to obtain the conversion rate between the specified currency unit and the currency unit of the cost set for the paywall at the time the request is made; and calculates the payment amount of the cost using the conversion rate.

5. An information processing system according to any one of claims 1 to 4, wherein the smart contract of the blockchain system, in the payment processing, transfers assets corresponding to the payment amount from the viewer's wallet address to the poster's receiving wallet address without holding the assets, and determines whether the payment processing is successful or not based on whether the transfer transaction has been stored.

6. The information processing system of claim 5, wherein the script includes an affiliate reward setting for the content, and the smart contract transfers a portion of assets corresponding to the payment amount from the viewer's wallet address to the affiliate corresponding to the content as a referral fee, in accordance with the reward rate included in the reward setting.

7. An information processing system according to any one of claims 1 to 4, wherein the content is a blog, a news site, or a corporate public relations page containing text, images, video, or audio.

8. An information processing method in a system including: a server device that provides a web application that accepts the creation and editing of content and distributes the created content; a first client device of a content contributor that uses the web application; a second client device of a viewer of content distributed from the server device; and a blockchain system connected to the server device and the second client device, wherein the first client device embeds a paywall script in an arbitrary location in the content it creates; when the second client device requests the removal of the paywall for the target content, a smart contract in the blockchain system executes a payment process for the cost from the viewer's wallet address to the contributor's wallet address using the script; and when the server device confirms a record of the successful payment process in the smart contract, it sends data of the target content after the paywall has been removed to the second client device.

9. A computer program that causes a computer that executes a web browser program to accept the creation and editing of content on the web browser program, and to execute a process of embedding a paywall script in any location of the content, wherein the script causes a smart contract in a blockchain system to execute a process of paying the cost from the wallet address of the viewer of the content to the wallet address of the poster, and when a record of the successful payment process in the smart contract is confirmed, to execute a process of sending the data of the content after the paywall has been removed to the viewer.

Images